From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: VFP handling in multiplatform feroceon kernels
Date: Tue, 24 Jun 2014 17:01:08 +0200 [thread overview]
Message-ID: <4861343.lqFLZvsPzW@wuerfel> (raw)
In-Reply-To: <alpine.LFD.2.11.1406241050390.16842@knanqh.ubzr>
On Tuesday 24 June 2014 10:56:44 Nicolas Pitre wrote:
> On Tue, 24 Jun 2014, Russell King - ARM Linux wrote:
>
> > As I point out, the problem is that if we build a kernel with ARM926
> > plus Feroceon support (thus including some of the Feroceon platforms),
> > and omitting the plagerised ID, how do we stop the potential data
> > corruption occuring should we boot on a Feroceon platform with the
> > old IDs.
>
> That's a valid concern.
>
> I don't know if all the Feroceon CPU cores are buggy wrt the VFP,
> however only some of the Orion5x platforms had a Feroceon core using the
> plagerised ID. Probably those two issues should be handled separately.
>
> So for the later I'd simply forbid any Orion5x platforms from being part
> of a multi-platform kernel.
We should definitely allow building a multiplatform kernel with both
Orion5x and Kirkwood, but we could make Orion5x conditional on ARM926
being disabled. Or we add a runtime-check in the Orion code to ensure
it only gets booted with the new CPU ID if ARM926 is enabled.
Arnd
next prev parent reply other threads:[~2014-06-24 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:17 VFP handling in multiplatform feroceon kernels Arnd Bergmann
2014-06-24 13:31 ` Andrew Lunn
2014-06-24 13:47 ` Arnd Bergmann
2014-06-24 13:42 ` Catalin Marinas
2014-06-24 13:57 ` Arnd Bergmann
2014-06-24 14:04 ` Nicolas Pitre
2014-06-24 14:10 ` Catalin Marinas
2014-06-24 14:14 ` Russell King - ARM Linux
2014-06-24 14:25 ` Catalin Marinas
2014-06-24 14:32 ` Arnd Bergmann
2014-06-24 14:45 ` Nicolas Pitre
2014-06-24 14:35 ` Russell King - ARM Linux
2014-06-24 14:56 ` Nicolas Pitre
2014-06-24 15:01 ` Arnd Bergmann [this message]
2014-06-24 14:49 ` Nicolas Pitre
2014-06-24 14:56 ` Arnd Bergmann
2014-06-24 14:08 ` Russell King - ARM Linux
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=4861343.lqFLZvsPzW@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