[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <6d9bb65c-d693-4d99-8183-b605cabf9380@app.fastmail.com>
Date: Wed, 01 Oct 2025 22:52:05 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Franz-Josef Haider" <fj.haider@...look.com>,
"Linus Walleij" <linus.walleij@...aro.org>
Cc: "Russell King" <linux@...linux.org.uk>,
"Ard Biesheuvel" <ardb@...nel.org>,
"Russell King" <rmk+kernel@...linux.org.uk>,
"Eric Biggers" <ebiggers@...nel.org>,
"Nathan Chancellor" <nathan@...nel.org>,
"Steven Rostedt" <rostedt@...dmis.org>, "Kees Cook" <kees@...nel.org>,
"Dave Vasilevsky" <dave@...ilevsky.ca>, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: Re: [PATCH] ARM: Make sure CPU_ARM940T kernel can be built.
On Wed, Oct 1, 2025, at 18:04, Franz-Josef Haider wrote:
> On 9/30/25 15:09, Linus Walleij wrote:
>> On Thu, Sep 25, 2025 at 11:33 PM Franz-Josef Haider <fj.haider@...look.com> wrote:
>>
>>> From 33ce5a26ef08199625bc5bb01a176047bfacff91 Mon Sep 17 00:00:00 2001
>>> From: Franz-Josef Haider <fj.haider@...look.com>
>
> Hello, I have done this change because when trying to "select
> CPU_ARM940T" from a Kconfig for a device with arm940t cpu, the build
> ends up failing with errors like
> arch/arm/lib/ashldi3.S: Assembler messages:
> arch/arm/lib/ashldi3.S:44: Error: cannot honor width suffix
> -- `rsb ip,r2,#32'
>
> With the change I am able to build a kernel which runs on a device with
> arm940t cpu (with the patch "ARM: Add missing mmu flags entry to arm940
> proc info." which I've submitted as well. And with the necessary mach
> files etc).
>
> I can elaborate on this in the commit message and also adjust the
> condition to include the other CPU types you mentioned.
Hi Franz-Josef,
We removed support for ARMv4T NOMMU a couple of years ago in
commit 2f618d5ef5dd ("ARM: remove support for NOMMU ARMv4/v5"),
in order to simplify the Kconfig CPU selection.
Adding a new platform in turn means you'll have to add that
infrastructure we skipped back then, and the dependency here
is only a very small part of that.
Do you have a public git tree with the rest of your patches?
Arnd
Powered by blists - more mailing lists