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, 16 Mar 2011 22:18:36 +0900 [thread overview]
Message-ID: <4D80B8AC.8030501@pobox.com> (raw)
In-Reply-To: <AANLkTimDL_MrFaqjyCJTYXkEsHaCQ8fD1MH1vX+Uots+@mail.gmail.com>
On 3/15/11 10:20 PM, Daniel Schwierzeck wrote:
>> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/81572/focus=81735
>
> sorry, I missed that discussion
You can find a lot more in the list archive.
> Do we need this endianess flag stuff at all? Each toolchain that is
> built with a specific
> endinaness does not really need the extra setting of -EB/-EL or am I
> miss something?
True, as far as toolchain-default-endianness build goes.
The Linux/MIPS kernel however is maintained where Big-Endian and Little-
-Endian machines can be configured and compiled using a single toolchain,
regardless of its default endianness. CONFIG_LITTLE_ENDIAN is exactly
for that purpose.
next prev parent reply other threads:[~2011-03-16 13:18 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 [this message]
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
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=4D80B8AC.8030501@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