linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: remove ARM710 specific assembler code
Date: Tue, 20 May 2014 17:14:04 +0100	[thread overview]
Message-ID: <20140520161403.GA28293@arm.com> (raw)
In-Reply-To: <20140520164819.63357114@alan.etchedpixels.co.uk>

On Tue, May 20, 2014 at 04:48:19PM +0100, One Thousand Gnomes wrote:
> > 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.
> 
> Why do you care ?

For now, just some negative diffstats in the arm tree ;). Longer term,
supporting only ARMv6+ could bring further core arm code clean-up but
that's not planned for another ~20 years.

> Worry about it at the point nobody can remember needing
> the support, or when it creates some horrible situation that is painful
> to keep supporting and nobody seems to care. We've only recently dropped
> 80386 support, and we still support MC68000.

It's not necessarily how far back we go but rather the wide variation in
ARM processors implementation, especially for the older architecture
versions, and not knowing whether the code still works since no-one
seems to remember having such hardware.

> Or just wait until 2038 approaches and the 32bit panic stations begins,
> then clean out 8)

This kind of matches my proposal to remove ARMv5 support in 20 years
(though we still keep ARMv6 and ARMv7 with 32-bit).

Anyway, the feedback seems to be that we keep them around until they can
no longer be supported (which probably means compiled).

-- 
Catalin

  reply	other threads:[~2014-05-20 16:14 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
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 [this message]
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=20140520161403.GA28293@arm.com \
    --to=catalin.marinas@arm.com \
    --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).