From: fainelli@broadcom.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: BCM: Restrict Broadcom BCM470X / BCM5301X to non-LPAE
Date: Tue, 14 Jul 2015 14:29:31 -0700 [thread overview]
Message-ID: <55A57F3B.1080909@broadcom.com> (raw)
In-Reply-To: <4793510.M34v5PmKgi@wuerfel>
On 14/07/15 13:43, Arnd Bergmann wrote:
> On Tuesday 14 July 2015 11:12:15 Florian Fainelli wrote:
>> Cortex-A9 on at least BCM4708 SoCs are not LPAE capable, booting such a
>> kernel will result in the following:
>>
>> Error: Kernel with LPAE support, but CPU does not support LPAE.
>>
>> Restrict such SoCs to be built in a configuration that does not enable
>> ARM_LPAE.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>>
>
> This is an old problem for all platforms, I think we want a more
> generic solution though, instead of adding the !LPAE dependency
> for each Cortex-A5/8/9 platform.
Fair enough, what do you have in mind? Should we introduce something
like CONFIG_V7_A9 and such, and update all platforms to select such
symbols such that we can then apply a restriction on other symbols if
there needs to be?
What if any of these CPUs end-up supporting LPAE, but this cannot be
flagged at build time?
--
Florian
next prev parent reply other threads:[~2015-07-14 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 18:12 [PATCH] ARM: BCM: Restrict Broadcom BCM470X / BCM5301X to non-LPAE Florian Fainelli
2015-07-14 20:43 ` Arnd Bergmann
2015-07-14 21:29 ` Florian Fainelli [this message]
2015-07-15 10:08 ` Arnd Bergmann
2015-07-15 16:38 ` Florian Fainelli
2015-07-15 20:41 ` Arnd Bergmann
2015-07-15 20:58 ` Gregory Fong
2015-07-15 21:00 ` Russell King - ARM Linux
2015-07-16 14:37 ` 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=55A57F3B.1080909@broadcom.com \
--to=fainelli@broadcom.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).