From: Shinya Kuribayashi <skuribay@pobox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/5] MIPS: Optimize the setup of endianess and CPU optimization flags
Date: Wed, 23 Mar 2011 23:51:10 +0900 [thread overview]
Message-ID: <4D8A08DE.3060900@pobox.com> (raw)
In-Reply-To: <AANLkTi=h0W1pur=mMRh4fsKPkKuGhksJnXWKs_6OFHPB@mail.gmail.com>
On 03/21/2011 09:42 PM, Daniel Schwierzeck wrote:
> I did some researching and testing with ELDK-4.1, ELDK-4.0 and ELDK-3.1.1.
Thanks, much appreciated.
> In ELDK-3.1.1 we have:
> - mips_4KC-gcc (GCC) 3.3.3 (DENX ELDK 3.1.1 3.3.3-9)
> - GNU assembler 2.14 20030612
>
> Therefore mips32r2 is already supported. But there is another problem
> with this binutils version. The latest additions to mips.lds and
> u-boot.lds for supporting recent binutils are causing parse errors.
I wonder what's that 'the latest additions to mips.lds and u-boot.lds
for supporting recent binutils' to be exact. Which commit(s) are you
referring to? Or could you provide error logs just in case please?
> Thus ELDK-3.1.1 and earlier are not functional with mainline U-Boot
> anyway. ELDK-4.0 and 4.1 with gcc-4.0.0 and binutils-2.16.1 are
> working properly.
>
> I suggest to drop official support for ELDK-3.1.1 / binutils-2.14 and
> earlier.
Hmm. According to the README file, even the Linux kernel still builds
with at least gcc 3.2. I'm feeling that it might be a bit too early to
drop gcc 3.3.3 (ELDK-3.1.1).
So I'd like to take a look at the issue you found this time, first. If
it's easy to fix, let's fix it. And if not, revise the patch please.
We have not heard of any problem reports on MIPS builds with ELDK-3.1.1
so far (at least I'm not aware of them). The change won't be a problem.
next prev parent reply other threads:[~2011-03-23 14:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 21:14 [U-Boot] [PATCH v2 0/5] MIPS: Refactoring of CPU and SoC code daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 1/5] MIPS: Purple: Remove Purple support daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 2/5] MIPS: Move content of arch/mips/cpu to arch/mips/cpu/mips32 daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 3/5] MIPS: Optimize the setup of endianess and CPU optimization flags daniel.schwierzeck at googlemail.com
2011-03-14 23:54 ` Shinya Kuribayashi
2011-03-15 13:20 ` Daniel Schwierzeck
2011-03-16 13:18 ` Shinya Kuribayashi
2011-03-16 14:41 ` Daniel Schwierzeck
2011-03-17 14:02 ` Shinya Kuribayashi
2011-03-17 15:20 ` Daniel Schwierzeck
2011-03-21 12:42 ` Daniel Schwierzeck
2011-03-23 14:51 ` Shinya Kuribayashi [this message]
2011-03-23 16:37 ` Daniel Schwierzeck
2011-03-28 14:56 ` Shinya Kuribayashi
2011-03-28 15:27 ` Daniel Schwierzeck
2011-03-28 15:58 ` Shinya Kuribayashi
2011-03-28 16:11 ` Daniel Schwierzeck
2011-03-14 21:14 ` [U-Boot] [PATCH v2 4/5] MIPS: IncaIP: Move all IncaIP specific code to separate subdirectory daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 5/5] MIPS: Au1x00: Move all Au1x00 " daniel.schwierzeck at googlemail.com
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=4D8A08DE.3060900@pobox.com \
--to=skuribay@pobox.com \
--cc=u-boot@lists.denx.de \
/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