mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
	linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: remove ARM710 specific assembler code
Date: Sat, 17 May 2014 10:46:36 +0100	[thread overview]
Message-ID: <20140517094636.GP3693@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140517092337.GA67711@MacBook-Pro.local>

On Sat, May 17, 2014 at 10:23:37AM +0100, Catalin Marinas wrote:
> On Fri, May 16, 2014 at 01:55:46PM +0100, Russell King - ARM Linux wrote:
> > There was a CPU called the ARM710, it was ARMv3 and it had no Thumb support.
> > 
> > There is also a CPU called the ARM710T, which is ARMv4 and has Thumb support.
> > 
> > These are two completely different CPUs, the former was removed along with
> > the removal of ARMv3 support.  The latter remains because we still support
> > ARMv4.
> 
> BTW, while clearly this patch was removing code for the wrong reasons, I
> think we should set a longer term timeline for getting rid of some of
> old features. Let's say in 10 years time we remove everything ARMv4,
> another 10 years ARMv5 and so on. We could make these milestones shorter
> but it really depends on what people use, we should not force them out
> of the kernel if still in use.

I still use StrongARM based machines here, and I don't see that changing
unless some suitably designed ARM boards come my way which (a) offer the
same features and (b) out perform it.

The problem is that there's lots of ARM boards which satisfy (b) - the
iMX6 stuff clearly does - but hardly anything which satisfies (a).

There's also been some recent effort with SA1100 SoC code, so there's
also other interest there still.

So, ARMv4 is still very much in use with modern kernels.

The difference between what you're proposing and what happened to ARMv3
is that ARMv3 was broken for quite some time (we read from some of the
CP15 registers which are read-only in ARMv3) and no one ever raised a
problem with that.  So, after a sufficient period of time, it got removed
- and no one batted an eyelid.  That's the correct way to do it - allow
code to age, and if no one notices it's been broken, then it can be
removed.

That process is slightly broken by the automated build testing we now
have (provided people are looking at the results.)

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-05-17  9:47 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 [this message]
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
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=20140517094636.GP3693@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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

Powered by JetHome