linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	Anshuman Khandual <anshuman.khandual@arm.com>
Subject: Re: [PATCH 2/2] ARM: remove support for NOMMU ARMv4/v5
Date: Wed, 9 Mar 2022 17:38:19 +0100	[thread overview]
Message-ID: <CAK8P3a3L2sfi-VQ=yjRhkGA6x6JTvCw5KyHQnBf2r348MX_avw@mail.gmail.com> (raw)
In-Reply-To: <08232117-7444-55d8-e13c-b49828c8f3e9@arm.com>

On Wed, Mar 9, 2022 at 5:21 PM Vladimir Murzin <vladimir.murzin@arm.com> wrote:
> On 3/9/22 4:17 PM, Arnd Bergmann wrote:
> > On Wed, Mar 9, 2022 at 4:48 PM Robin Murphy <robin.murphy@arm.com> wrote:
> >>
> >> On 2022-03-09 14:40, Arnd Bergmann wrote:
> >>> From: Arnd Bergmann <arnd@arndb.de>
> >>>
> >>> It is possible to build MMU-less kernels for Cortex-M base
> >>> microcrontrollers as well as a couple of older platforms that
> >>> have not been converted to CONFIG_ARCH_MULTIPLATFORM,
> >>> specifically ep93xx, footbridge, dove, sa1100 and s3c24xx.
> >>>
> >>> It seems unlikely that anybody has tested those configurations
> >>> in recent years, as even building them is frequently broken.
> >>> A patch I submitted caused another build time regression
> >>> in this configuration. I sent a patch for that, but it seems
> >>> better to also remove the option entirely, leaving ARMv7-M
> >>> as the only supported Arm NOMMU target for simplicity.
> >>
> >> In that case, it would probably make sense to garbage-collect all the
> >> configs, setup code and other stuff relating to older MMU-less CPU cores
> >> like ARM1156, ARM940, etc. at the same time.
> >
> > Right, good idea. These are only selected by CONFIG_ARCH_INTEGRATOR,
> > but that in turn doesn't build for CONFIG_MMU=n because it depends on
> > ARCH_MULTIPLATFORM. I'll send a patch for these.
> >
> > I also went back and forth between removing the #ifdefs in
> > arch/arm/mm/proc-*.S for this patch, though I did not do that in the end.
> > We may still want them at least for proc-v7.S because that is a small
> > chance that someone will want to support Cortex-R.
> >
>
> I'd appreciate if you keep them since I run Cortex-R52...

Ok, no problem.

Any opinion on removing CPU_ARM{7TDMI,740T,940T,946E}?

       Arnd

  reply	other threads:[~2022-03-09 16:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 14:40 [PATCH 1/2] ARM: fix building NOMMU ARMv4/v5 kernels Arnd Bergmann
2022-03-09 14:40 ` [PATCH 2/2] ARM: remove support for NOMMU ARMv4/v5 Arnd Bergmann
2022-03-09 15:48   ` Robin Murphy
2022-03-09 16:17     ` Arnd Bergmann
2022-03-09 16:21       ` Vladimir Murzin
2022-03-09 16:38         ` Arnd Bergmann [this message]
2022-03-10  1:29           ` Linus Walleij
2022-03-10  1:22       ` Linus Walleij
2022-03-10  9:23         ` Arnd Bergmann
2022-03-10 14:21           ` Robin Murphy
2022-03-14 23:00           ` Linus Walleij
2022-03-15  7:27             ` Arnd Bergmann
2022-03-10  1:19 ` [PATCH 1/2] ARM: fix building NOMMU ARMv4/v5 kernels Linus Walleij
2022-03-12  9:14 ` Ard Biesheuvel

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='CAK8P3a3L2sfi-VQ=yjRhkGA6x6JTvCw5KyHQnBf2r348MX_avw@mail.gmail.com' \
    --to=arnd@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robin.murphy@arm.com \
    --cc=tglx@linutronix.de \
    --cc=vladimir.murzin@arm.com \
    /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).