From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: remove ARM710 specific assembler code
Date: Tue, 20 May 2014 22:09:48 +0200 [thread overview]
Message-ID: <4437236.32BrGIk46D@wuerfel> (raw)
In-Reply-To: <20140520160512.GE27830@atomide.com>
On Tuesday 20 May 2014 09:05:13 Tony Lindgren wrote:
> * Arnd Bergmann <arnd@arndb.de> [140519 04:27]:
> > On Saturday 17 May 2014 10:56:02 Catalin Marinas wrote:
> >
> > For the case of ARM710T, I think the last remaining user that can be
> > configured is mach-integrator, but I don't know if anybody even has that
> > CPU tile, or wants to keep using it. If Russell and Linus as the only
> > people that have cared about Integrator in the past years want to
> > cut down the number of supported CPUs, that would be a different matter:
> > quite a number of CPUs are not supported in any other platform.
> > Note that the integrator target in qemu does not support any ARM7, only
> > StrongARM, ARM9 or later. I also double-checked about mach-clps711x,
> > but I'm pretty sure those SoCs are all either ARM710a (no longer supported)
> > or ARM720T (quite active).
>
> Hmm I don't think mach-integrator is using ARM710T?
I don't know, we don't have a separate Kconfig option, so ARM710T and ARM720T
use the same CONFIG_CPU_ARM720T symbol that can be enabled for integrator.
Without any further information, I assumed that both might potentially be used.
> The ARM710T was done by NEC and was used by the Psion MX hardware.
> It's very close to ARM720T as far as I remember so might as well keep
> the CPU support for it as that's just a few lines of code in the
> mainline kernel.
>
> I don't think we have any mach directories using ARM710T, but I
> would not be surprised if somebody comes along with device tree
> based booting patches for Psion MX at some point.
Of course, if someone does this, the CPU support would be the least
of their work ;-)
Just out of curiosity: was that NEC 710T a SoC that replaced the
CL/PS7110, or a standalone CPU that Psion combined with a custom
ASIC?
Arnd
next prev parent reply other threads:[~2014-05-20 20:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 21:46 [PATCH] ARM: remove last use of CONFIG_CPU_ARM710 Paul Bolle
2014-05-14 8:24 ` [PATCH] [RESEND] " Paul Bolle
2014-05-14 8:48 ` Alexander Shiyan
2014-05-14 9:07 ` Paul Bolle
2014-05-14 9:17 ` Arnd Bergmann
2014-05-14 9:25 ` Paul Bolle
2014-05-14 9:28 ` Arnd Bergmann
2014-05-16 9:29 ` [PATCH] ARM: remove ARM710 specific assembler code Paul Bolle
2014-05-16 12:55 ` Russell King - ARM Linux
2014-05-16 14:50 ` Paul Bolle
2014-05-17 9:23 ` Catalin Marinas
2014-05-17 9:46 ` Russell King - ARM Linux
2014-05-17 9:56 ` Catalin Marinas
2014-05-17 10:26 ` Russell King - ARM Linux
2014-05-19 10:18 ` Catalin Marinas
2014-05-19 11:26 ` Arnd Bergmann
2014-05-20 16:05 ` Tony Lindgren
2014-05-20 20:09 ` Arnd Bergmann [this message]
2014-05-22 18:40 ` Tony Lindgren
2014-05-22 18:42 ` Tony Lindgren
2014-05-20 15:48 ` One Thousand Gnomes
2014-05-20 16:14 ` Catalin Marinas
2014-05-23 9:07 ` [PATCH] [RESEND] ARM: remove last use of CONFIG_CPU_ARM710 Paul Bolle
2014-05-23 9:22 ` 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=4437236.32BrGIk46D@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