From: Michael Ellerman <mpe@ellerman•id.au>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: Boqun Feng <boqun.feng@gmail•com>,
linuxppc-dev@lists•ozlabs.org, Paul Mackerras <paulus@samba•org>,
Geoff Levand <geoff@infradead•org>,
Anatolij Gustschin <agust@denx•de>,
Alistair Popple <alistair@popple•id.au>,
Matt Porter <mporter@kernel•crashing.org>,
Vitaly Bordug <vitb@kernel•crashing.org>,
Scott Wood <scottwood@freescale•com>,
Kumar Gala <galak@kernel•crashing.org>,
Olof Johansson <olof@lixom•net>, Arnd Bergmann <arnd@arndb•de>
Subject: Re: [Question] Is little endian supported on all the platforms?
Date: Tue, 01 Sep 2015 11:31:29 +1000 [thread overview]
Message-ID: <1441071089.26730.4.camel@ellerman.id.au> (raw)
In-Reply-To: <1441053636.2720.21.camel@kernel.crashing.org>
On Tue, 2015-09-01 at 06:40 +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2015-08-31 at 21:19 +1000, Michael Ellerman wrote:
>
> > Yes. Maybe something like this?
>
> I would have done it the other way around with endian at the top
> and only the supported platforms displayed based on the endian...
>
> But I don't care *that* much either way
Yeah, I figured folks are not really caring so much about endian when
configuring they're primarily thinking about the platform.
But if we do it this way we *also* need to make PS3 etc. depend on
BIG_ENDIAN, so they don't get enabled on multi-platform LE builds, so we should
probably just do it that way.
cheers
prev parent reply other threads:[~2015-09-01 1:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:44 [Question] Is little endian supported on all the platforms? Boqun Feng
2015-08-31 6:52 ` Benjamin Herrenschmidt
2015-08-31 7:53 ` Boqun Feng
2015-08-31 8:31 ` Benjamin Herrenschmidt
2015-08-31 11:19 ` Michael Ellerman
2015-08-31 11:56 ` Boqun Feng
2015-09-01 1:39 ` Michael Ellerman
2015-08-31 12:12 ` Cédric Le Goater
2015-09-01 7:39 ` Boqun Feng
2015-08-31 20:40 ` Benjamin Herrenschmidt
2015-09-01 1:31 ` Michael Ellerman [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=1441071089.26730.4.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=agust@denx$(echo .)de \
--cc=alistair@popple$(echo .)id.au \
--cc=arnd@arndb$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=boqun.feng@gmail$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=geoff@infradead$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mporter@kernel$(echo .)crashing.org \
--cc=olof@lixom$(echo .)net \
--cc=paulus@samba$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
--cc=vitb@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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