From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: mol@pengutronix.de, distrokit@pengutronix.de,
antonynpavlov@gmail.com, pmamonov@gmail.com
Subject: Re: [DistroKit] [PATCH v2 0/2] add MIPS platform support
Date: Wed, 5 Feb 2020 14:53:22 +0100 [thread overview]
Message-ID: <94abde6b-080f-d347-fe8c-bb77753ed492@pengutronix.de> (raw)
In-Reply-To: <20200205132221.GA1916864@lenoch>
On 05.02.20 14:22, Ladislav Michl wrote:
> On Wed, Feb 05, 2020 at 02:08:31PM +0100, Oleksij Rempel wrote:
>>
>>
>> On 05.02.20 14:01, Ladislav Michl wrote:
>>> On Wed, Feb 05, 2020 at 01:58:03PM +0100, Oleksij Rempel wrote:
>>>> v2:
>>>> - add doc/hardware_mips_qemu.rst
>>>> - fix kernel boot without barebox
>>>>
>>>> This is initial MIPS support for MIPSr2 BE soft float platform.
>>>> Currently it was tested only with barebox and will need more effort to
>>>> make it work with linux.
>>>
>>> Any objections making SGI Indy, Indigo2 and O2 support mainline?
>>> As I'm probably the only user I do not eventually want to hold back
>>> development making changes not usefull to others :)
>>
>> I have nothing against it. Will it work with toolchains we already have? Can
>> we share same kernel and rootfs binaries for this machines?
>
> Toolchains and rootfs can be the same, however kernels are different,
> SGI Indy is IP22, while SGI O2 is IP32. They are using ARCS firmware
> ("bootloader"). For those curious, more info:
> https://www.linux-mips.org/wiki/IP22
> https://www.linux-mips.org/wiki/IP32
This should be possible. We will prepare an example how this can be done properly.
Kind regards,
Oleksij Rempel
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
prev parent reply other threads:[~2020-02-05 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 12:58 Oleksij Rempel
2020-02-05 12:58 ` [DistroKit] [PATCH v2 1/2] platform-mips: add basic qemu malta support Oleksij Rempel
2020-02-05 12:58 ` [DistroKit] [PATCH v2 2/2] platform-mips: libffi version 3.3 Oleksij Rempel
2020-02-05 13:01 ` [DistroKit] [PATCH v2 0/2] add MIPS platform support Ladislav Michl
2020-02-05 13:08 ` Oleksij Rempel
2020-02-05 13:22 ` Ladislav Michl
2020-02-05 13:53 ` Oleksij Rempel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94abde6b-080f-d347-fe8c-bb77753ed492@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=distrokit@pengutronix.de \
--cc=ladis@linux-mips.org \
--cc=mol@pengutronix.de \
--cc=pmamonov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox