From: Joel Sherrill <Joel.Sherrill@OARcorp.com>
To: Ralf Corsepius <ralf.corsepius@googlemail.com>
Cc: Jia Liu <proljc@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
"ralf.corsepius@rtems.org" <ralf.corsepius@rtems.org>,
"rdsandiford@googlemail.com" <rdsandiford@googlemail.com>
Subject: Re: [PATCH] [MIPS] Add mips*el-rtems stubs
Date: Tue, 30 Oct 2012 12:25:00 -0000 [thread overview]
Message-ID: <3o7tblocxeouvftq579o05qf.1351599806338@email.android.com> (raw)
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.
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
next reply other threads:[~2012-10-30 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 12:25 Joel Sherrill [this message]
2012-10-30 13:52 ` Jia Liu
2012-12-07 1:12 ` Jia Liu
-- strict thread matches above, loose matches on Subject: below --
2012-10-28 6:26 Jia Liu
2012-10-30 11:21 ` Richard Sandiford
2012-10-30 12:19 ` Ralf Corsepius
2012-12-31 9:48 ` Devin
2012-12-31 13:49 ` Ralf Corsepius
2013-01-04 3:06 ` Devin
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=3o7tblocxeouvftq579o05qf.1351599806338@email.android.com \
--to=joel.sherrill@oarcorp.com \
--cc=binutils@sourceware.org \
--cc=proljc@gmail.com \
--cc=ralf.corsepius@googlemail.com \
--cc=ralf.corsepius@rtems.org \
--cc=rdsandiford@googlemail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).