linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gang.chen.5i5j@gmail.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arch: Kconfig: Let all little endian architectures define CPU_LITTLE_ENDIAN explicitly
Date: Tue, 12 Aug 2014 11:27:42 +0800	[thread overview]
Message-ID: <53E989AE.7070808@gmail.com> (raw)
In-Reply-To: <20140811225326.GF30401@n2100.arm.linux.org.uk>



On 8/12/14 6:53, Russell King - ARM Linux wrote:
> On Tue, Aug 12, 2014 at 05:18:44AM +0800, Chen Gang wrote:
>> x86, ia64, and arm(64) are little endian, and also another architectures
>> may be little endian (mips, sh, powerpc, and m32r) which already marked
>> CPU_LITTLE_ENDIAN explicitly.
> 
> This is incorrect.  ARM can be either endian.
> 
> arch/arm/mm/Kconfig:
> 
> config CPU_BIG_ENDIAN
>         bool "Build big-endian kernel"
>         depends on ARCH_SUPPORTS_BIG_ENDIAN
>         help
>           Say Y if you plan on running a kernel in big-endian mode.
>           Note that your board must be properly built and your board
>           port must properly enable any big-endian related features
>           of your chipset/board/processor.
> 

OK, thanks, I shall check all CPU_BIG_ENDIAN and send patch v2 for it.

And still welcome another ideas, suggestions or completions, especially
for another architectures.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

      reply	other threads:[~2014-08-12  3:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 21:18 [PATCH] arch: Kconfig: Let all little endian architectures define CPU_LITTLE_ENDIAN explicitly Chen Gang
2014-08-11 22:53 ` Russell King - ARM Linux
2014-08-12  3:27   ` Chen Gang [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=53E989AE.7070808@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).