Re: [PATCH] [MIPS] Add mips*el-rtems stubs

[Jia Liu <proljc at gmail dot com>]

Hi Joel, Ralf

On Tue, Oct 30, 2012 at 8:24 PM, Joel Sherrill
<Joel.Sherrill@oarcorp.com> wrote:
> I agree with Ralf.
>
> Jai. Post the entire tool chain patch set and RTEMS changes to the rtems-devel mailing list. For something like this, we just want to make sure all the bits are there and line up.
>

I've sent the RTEMS patch to rtems-devel@rtems.org, but, somehow, it didn't
appeared in the rtems-devel Archives, what's wrong with me or my friend?
May you have a check? The mail subject is  [PATCH] mips*el support .

> Then once that review is done, it can go upstream.
>
> --joel
>
> Ralf Corsepius <ralf.corsepius@googlemail.com> wrote:
>
>
> On 10/30/2012 12:21 PM, Richard Sandiford wrote:
>> Jia Liu <proljc@gmail.com> writes:
>>> Hi all,
>>>
>>> I'm working on several MIPS64-based processors, RTEMS is a part of my SDK.
>>> When I build a mips64el toolchain for RTEMS, I found that mips*el support
>>> has beed removed, so, I try to take it back.
>  >>
>>> This patch is tested, and the RTEMS patch will summitted by a friend at ICT.
>>
>> This looks good in principle.  It was Ralf (cc:ed) who removed the port
>> originally,
>
> I don't recall me having done so ;) It probably was removed, because
> there currently is no mips*el port in RTEMS
>
>> so once he's happy that the port has indeed been resurrected
>> from an RTEMS POV,
> Well, I don't have any problem in a mips64el target being added to RTEMS
> and its toolchains, but so far, this does not apply.
>
>> I'll go ahead and apply it.
> I am uncertain on how to proceed. Without the missing other components
> (RTEMS, newlib, gcc (+ gdb)) also being submitted, adding a mips64el to
> binutils doesn't make much sense.
>
> Ralf
>

Regards,
Jia.