linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: BCM: Restrict Broadcom BCM470X / BCM5301X to non-LPAE
Date: Wed, 15 Jul 2015 22:41:51 +0200	[thread overview]
Message-ID: <5941809.XWvPzT6esn@wuerfel> (raw)
In-Reply-To: <55A68C9C.8000303@gmail.com>

On Wednesday 15 July 2015 09:38:52 Florian Fainelli wrote:
> 
> I like the idea in general, but I think this is going to be a very
> tedious job to collect every single CR values for ARMv7 processors to
> determine whether they are pure v7 or v7e... Maybe we could use
> kernelci.org to start extracting the relevant lines in bootlogs and
> people can start adding their own chips one by one?

No, we know most of them:

Cortex-A5, A8, A9: ARMv7, no LPAE, no IDIV
Cortex-A7, A15, A12, A17: ARMv7VE, no LPAE, no IDIV


Almost everyone uses the above cores unmodified.

The ones I'm not 100% sure about are:

Marvell PJ4 (almost certainly ARMv7)
Marvell PJ4B (probably ARMv7 plus IDIV without LPAE)
Qualcomm Scorpion (probably ARMv7)
Qualcomm Krait (probably ARMv7 plus IDIV without LPAE)
Broadcom Brahma-B15 (almost certainly ARMv7VE)

We basically just need to find out from the mach-qcom and
mach-mvebu maintainers what combination of LPAE and IDIV
they need to support, and you can find out about B15.

If my list above is correct, there are no CPUs that have
LPAE but don't have IDIV, and we just need to decide how
to represent that.

	Arnd

  reply	other threads:[~2015-07-15 20:41 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
2015-07-15 10:08     ` Arnd Bergmann
2015-07-15 16:38       ` Florian Fainelli
2015-07-15 20:41         ` Arnd Bergmann [this message]
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=5941809.XWvPzT6esn@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;
as well as URLs for NNTP newsgroup(s).