From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Remove support for ARMv3 ARM610 and ARM710 CPUs
Date: Fri, 4 May 2012 15:46:43 +0100 [thread overview]
Message-ID: <20120504144643.GG26481@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201205041441.24573.arnd@arndb.de>
On Fri, May 04, 2012 at 02:41:24PM +0000, Arnd Bergmann wrote:
> On Friday 04 May 2012, Russell King - ARM Linux wrote:
> > This patch removes support for ARMv3 CPUs, which haven't worked properly
> > for quite some time (see the FIXME comment in arch/arm/mm/fault.c). The
> > only V3 parts left is the cache model for ARMv3, which is needed for some
> > odd reason by ARM740T CPUs, and being able to build with -march=armv3,
> > which is required for the RiscPC platform due to its bus structure.
>
> No objections to the patch, but I wonder if this change obsoletes any
> hardware drivers in turn. Are there any RiscPC peripherals that are
> only available on the older models?
"older models" ? It's not a machine where the CPU is soldered to the
motherboard. I could describe it as being like an x86 motherboard where
you can plug either an ARM610, ARM710 or StrongARM CPU into it. The
CPU type is merely incidental.
next prev parent reply other threads:[~2012-05-04 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 9:56 [RFC] Remove support for ARMv3 ARM610 and ARM710 CPUs Russell King - ARM Linux
2012-05-04 11:16 ` Will Deacon
2012-05-04 14:41 ` Arnd Bergmann
2012-05-04 14:46 ` Russell King - ARM Linux [this message]
2012-05-04 15:02 ` Russell King - ARM Linux
2012-05-04 15:33 ` Arnd Bergmann
2012-05-04 15:38 ` Russell King - ARM Linux
2012-05-04 15:20 ` Arnd Bergmann
2012-05-04 15:39 ` Jean-Christophe PLAGNIOL-VILLARD
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=20120504144643.GG26481@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).