From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
akpm@linux-foundation.org, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
vgupta@synopsys.com, Geert Uytterhoeven <geert@linux-m68k.org>,
Jean Delvare <jdelvare@suse.de>,
linux@arm.linux.org.uk, catalin.marinas@arm.com,
will.deacon@arm.com, hskinnemoen@gmail.com, egtvedt@samfundet.no,
realmz6@gmail.com, msalter@redhat.com, a-jacquiot@ti.com,
starvik@axis.com, jesper.nilsson@axis.com, dhowells@redhat.com,
rkuo@codeaurora.org, tony.luck@intel.com, fenghua.yu@intel.com,
takata@linux-m32r.org, james.hogan@imgtec.com,
Michal Simek <monstr@monstr.eu>,
yasutake.koichi@jp.panasonic.com, jonas@southpole.se,
jejb@parisc-linux.org, deller@gmx.de,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
paulus@samba.org, mpe@ellerman.id.au, Mart
Subject: Re: [PATCH v3] arch: Kconfig: Let all architectures set endian explicitly
Date: Fri, 15 Aug 2014 06:14:38 +0800 [thread overview]
Message-ID: <53ED34CE.3040001@gmail.com> (raw)
In-Reply-To: <20140814180418.GA20777@linux-mips.org>
On 08/15/2014 02:04 AM, Ralf Baechle wrote:
> On Fri, Aug 15, 2014 at 12:54:53AM +0800, Chen Gang wrote:
>
>> Normal architectures:
>>
>> - Big endian: avr32, frv, m68k, openrisc, parisc, s390, sparc
>>
>> - Little endian: alpha, blackfin, cris, hexagon, ia64, metag, mn10300,
>> score, unicore32, x86
>>
>> - Choose in config time: arc, arm, arm64, c6x, m32r, mips, powerpc, sh
>
> Nak for MIPS. On MIPS Kconfig already always sets one of CPU_BIG_ENDIAN
> and CPU_LITTLE_ENDIAN depending on platforms and where both endianess are
> supported by a platform, user choice:
>
> config FOO
> bool "foo"
> select SYS_SUPPORTS_LITTLE_ENDIAN
>
> config FOO
> bool "foo"
> select SYS_SUPPORTS_BIG_ENDIAN
> select SYS_SUPPORTS_LITTLE_ENDIAN
> [...]
> choice
> prompt "Endianess selection"
> help
> Some MIPS machines can be configured for either little or big endian
> byte order. These modes require different kernels and a different
> Linux distribution. In general there is one preferred byteorder for a
> particular system but some systems are just as commonly used in the
> one or the other endianness.
>
> config CPU_BIG_ENDIAN
> bool "Big endian"
> depends on SYS_SUPPORTS_BIG_ENDIAN
>
> config CPU_LITTLE_ENDIAN
> bool "Little endian"
> depends on SYS_SUPPORTS_LITTLE_ENDIAN
> help
>
> endchoice
>
OK, thanks, I assumes when support both endian, the default choice is
CPU_BIG_ENDIAN, although no default value for choice (originally, I did
worry about it).
> So I think you can just drop the MIPS segment from your patch.
>
If what I assumes is correct, what you said sounds reasonable to me.
Thanks.
--
Chen Gang
Open share and attitude like air water and life which God blessed
next prev parent reply other threads:[~2014-08-14 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 16:54 [PATCH v3] arch: Kconfig: Let all architectures set endian explicitly Chen Gang
2014-08-14 18:04 ` Ralf Baechle
2014-08-14 22:14 ` Chen Gang [this message]
2014-08-15 9:01 ` Chen Gang
2014-08-24 8:38 ` Chen Gang
2014-08-25 12:26 ` Chen Gang
2014-08-14 18:21 ` Vineet Gupta
2014-08-14 18:27 ` Lennox Wu
2014-08-14 22:22 ` Chen Gang
2014-08-14 23:12 ` Vineet Gupta
2014-08-15 1:29 ` Chen Gang
2014-08-15 1:47 ` Max Filippov
2014-08-15 1:52 ` Max Filippov
2014-08-15 2:06 ` Chen Gang
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=53ED34CE.3040001@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=a-jacquiot@ti.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=deller@gmx.de \
--cc=dhowells@redhat.com \
--cc=egtvedt@samfundet.no \
--cc=fenghua.yu@intel.com \
--cc=geert@linux-m68k.org \
--cc=hskinnemoen@gmail.com \
--cc=ink@jurassic.park.msu.ru \
--cc=james.hogan@imgtec.com \
--cc=jdelvare@suse.de \
--cc=jejb@parisc-linux.org \
--cc=jesper.nilsson@axis.com \
--cc=jonas@southpole.se \
--cc=linux@arm.linux.org.uk \
--cc=mattst88@gmail.com \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=msalter@redhat.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=realmz6@gmail.com \
--cc=rkuo@codeaurora.org \
--cc=rth@twiddle.net \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=tony.luck@intel.com \
--cc=vgupta@synopsys.com \
--cc=will.deacon@arm.com \
--cc=yasutake.koichi@jp.panasonic.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 NNTP newsgroup(s).