From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Xia Kaixu <kaixu.xia@linaro.org>,
arm@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/5] ARM: allow errata and XIP options to be enabled without ARCH_MULTIPLATFORM_STRICT
Date: Tue, 28 Oct 2014 14:31:18 +0000 [thread overview]
Message-ID: <20141028143118.GH27405@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <6893071.4YhqEbdaBz@wuerfel>
On Tue, Oct 28, 2014 at 03:24:38PM +0100, Arnd Bergmann wrote:
> On Tuesday 28 October 2014 14:02:31 Russell King - ARM Linux wrote:
> > On Tue, Oct 28, 2014 at 09:31:34PM +0800, Xia Kaixu wrote:
> > > With the ARCH_MULTIPLATFORM_STRICT option, it becomes much easier to
> > > enable the ERRATA options when we know at configuration time that we
> > > don't care about the generic case. The previous configuration makes
> > > XIP_KERNEL option fundamentally non-MULTIPLATFORM, but it's still
> > > valid to select it when building for !ARCH_MULTIPLATFORM_STRICT and
> > > selecting only the one machine that you want to run on.
> >
> > XIP_KERNEL isn't supported on anything past ARMv5 though.
>
> I would really like to get some of the platforms that currently use
> XIP_KERNEL to use ARCH_MULTIPLATFORM in the long run. One of them
> is EFM32, which is ARMv7-M.
Right, and on ARMv7-M, the restrictions against XIP_KERNEL don't apply.
The restrictions on XIP_KERNEL only apply with MMU-full kernels, because
of the remapping needed - the kernel is executed from flash, which is
mapped separately, and that mapping needs to be setup in order to turn
the MMU on.
With ARMv7-M, there is no MMU to worry about, no other mappings are
required, so there is no special platform specific setup applicable.
So, I don't see any reason why XIP_KERNEL can't depend on
!ARCH_MULTIPLATFORM || CPU_V7M.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-10-28 14:31 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
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 [this message]
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=20141028143118.GH27405@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kaixu.xia@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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