public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/5] ARM: restrict CPU_BIG_ENDIAN configuration option
Date: Tue, 28 Oct 2014 15:37:52 +0100	[thread overview]
Message-ID: <3137318.QMDnWOWDgo@wuerfel> (raw)
In-Reply-To: <20141028140021.GD27405@n2100.arm.linux.org.uk>

On Tuesday 28 October 2014 14:00:22 Russell King - ARM Linux wrote:
> On Tue, Oct 28, 2014 at 09:31:33PM +0800, Xia Kaixu wrote:
> > Some platforms don't work when CPU_BIG_ENDIAN is enabled.
> > So It can get a dependency on !ARCH_MULTIPLATFORM_STRICT.
> 
> What if big endian wants to build a multiplatform kernel?

They can turn off ARCH_MULTIPLATFORM_STRICT easily.
 
> This doesn't look right to me.  Instead, we should be arranging for
> those which do not work in BE mode to depend on !CPU_BIG_ENDIAN.
> Yes, it's a larger patch but IMHO is a much more correct solution.

I've also asked Kaixu to put this one in, mostly for the side-effect
of getting an allmodconfig kernel to be little-endian, but also
because we don't really know which platforms are ok to run on
big-endian. I would assume that most platforms have at least some
platform-specific drivers that are not endian-clean, and even if
the platform works big-endian in principle, it's unclear if
everything works.

The most important aspect is probably user space though: If you
build a multiplatform kernel (or one for ARMv4/5 and one for ARMv6/7)
that runs on all sorts of machines, you can have a common user space
that is built for ARMv4 little-endian and that will run everywhere.
As soon as you enable big-endian, you have a fundamental ABI change
and nothing works unless you replace the entire user space side.

	Arnd

  reply	other threads:[~2014-10-28 14:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 13:31 [PATCH v2 0/5] ARM: get a strict multiplatform kernel that can run on any hardware Xia Kaixu
2014-10-28 13:31 ` [PATCH v2 1/5] ARM: introduce a CONFIG_ARCH_MULTIPLATFORM_STRICT Kconfig option Xia Kaixu
2014-10-28 14:18   ` Arnd Bergmann
2014-10-28 14:21     ` Russell King - ARM Linux
2014-10-28 13:31 ` [PATCH v2 2/5] ARM: change the corresponding arm/mach defconfigs Xia Kaixu
2014-10-28 13:31 ` [PATCH v2 3/5] ARM: restrict CPU_BIG_ENDIAN configuration option Xia Kaixu
2014-10-28 14:00   ` Russell King - ARM Linux
2014-10-28 14:37     ` Arnd Bergmann [this message]
2014-10-28 14:53       ` Russell King - ARM Linux
2014-10-28 16:03         ` Arnd Bergmann
2014-10-28 13:31 ` [PATCH v2 4/5] ARM: allow errata and XIP options to be enabled without ARCH_MULTIPLATFORM_STRICT Xia Kaixu
2014-10-28 14:02   ` Russell King - ARM Linux
2014-10-28 14:24     ` Arnd Bergmann
2014-10-28 14:31       ` Russell King - ARM Linux
2014-10-28 14:50         ` Arnd Bergmann
2014-10-28 15:05           ` Russell King - ARM Linux
2014-10-28 15:32             ` Arnd Bergmann
2014-10-28 13:31 ` [PATCH v2 5/5] ARM: use early console instead of early debug in allmodconfig kernels Xia Kaixu
2014-10-28 14:05   ` Russell King - ARM Linux
2014-10-28 14:29     ` Arnd Bergmann
2014-10-28 14:35       ` Russell King - ARM Linux
2014-10-28 15:01         ` Arnd Bergmann

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=3137318.QMDnWOWDgo@wuerfel \
    --to=arnd@arndb.de \
    --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