From: "Arnd Bergmann" <arnd@arndb.de>
To: "Franz-Josef Haider" <fj.haider@outlook.com>,
"Linus Walleij" <linus.walleij@linaro.org>
Cc: "Russell King" <linux@armlinux.org.uk>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Russell King" <rmk+kernel@armlinux.org.uk>,
"Eric Biggers" <ebiggers@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Kees Cook" <kees@kernel.org>,
"Dave Vasilevsky" <dave@vasilevsky.ca>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] ARM: Make sure CPU_ARM940T kernel can be built.
Date: Wed, 01 Oct 2025 22:52:05 +0200 [thread overview]
Message-ID: <6d9bb65c-d693-4d99-8183-b605cabf9380@app.fastmail.com> (raw)
In-Reply-To: <VI0P195MB273993B2928F985EAC763375EDE6A@VI0P195MB2739.EURP195.PROD.OUTLOOK.COM>
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@outlook.com> wrote:
>>
>>> From 33ce5a26ef08199625bc5bb01a176047bfacff91 Mon Sep 17 00:00:00 2001
>>> From: Franz-Josef Haider <fj.haider@outlook.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
next prev parent reply other threads:[~2025-10-01 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 21:33 Franz-Josef Haider
2025-09-30 12:09 ` Linus Walleij
2025-10-01 16:04 ` Franz-Josef Haider
2025-10-01 19:14 ` Linus Walleij
2025-10-01 20:52 ` Arnd Bergmann [this message]
2025-10-02 15:34 ` Franz-Josef Haider
2025-10-02 23:02 ` Arnd Bergmann
2025-10-24 13:51 ` Franz-Josef Haider
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=6d9bb65c-d693-4d99-8183-b605cabf9380@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ardb@kernel.org \
--cc=dave@vasilevsky.ca \
--cc=ebiggers@kernel.org \
--cc=fj.haider@outlook.com \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nathan@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=trivial@kernel.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
all inboxes | Powered by JetHome®