From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
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: Mon, 31 Aug 2015 18:31:35 +1000 [thread overview]
Message-ID: <1441009895.2720.7.camel@kernel.crashing.org> (raw)
In-Reply-To: <20150831075340.GB1071@fixme-laptop.cn.ibm.com>
On Mon, 2015-08-31 at 15:53 +0800, Boqun Feng wrote:
> Got it, thank you ;-)
>
> So should we modify Kconfigs of all the platform to reflect this?
It would make sense to disable all platforms other than pseries and
powernv in LE, yes.
> > But the specific problem you are having looks like a differnet
> > issue
> > with the PS3 boot wrapper.
> >
>
> But could the reason of this be that the building process of the PS3
> boot wrapper assumes the kernel is BE?
Possibly something in the makefiles or the asm, I haven't looked.
Cheers,
Ben.
next prev parent reply other threads:[~2015-08-31 8:33 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 [this message]
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
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=1441009895.2720.7.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=agust@denx.de \
--cc=alistair@popple.id.au \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=geoff@infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=mporter@kernel.crashing.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=vitb@kernel.crashing.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.