From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Linus Walleij <linus.walleij@linaro.org>,
Richard Earnshaw <richard.earnshaw@arm.com>,
Richard Sandiford <richard.sandiford@arm.com>,
Ramana Radhakrishnan <ramanara@nvidia.com>,
Nicolas Pitre <nico@fluxnic.net>, Mark Brown <broonie@kernel.org>,
Kristoffer Ericson <kristoffer.ericson@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Janusz Krzysztofik <jmkrzyszt@gmail.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
Nikita Shubin <nikita.shubin@maquefel.me>,
linux-samsung-soc@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory Clement <gregory.clement@bootlin.com>,
"Jeremy J. Peper" <jeremy@jeremypeper.com>,
debian-arm@lists.debian.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Subject: Re: [RFC} arm architecture board/feature deprecation timeline
Date: Thu, 1 Aug 2024 10:04:06 +0200 [thread overview]
Message-ID: <f5e8b8ca-33c7-4725-b751-fc9d76959423@kernel.org> (raw)
In-Reply-To: <2831c5a6-cfbf-4fe0-b51c-0396e5b0aeb7@app.fastmail.com>
On 31/07/2024 19:29, Arnd Bergmann wrote:
> We removed a lot of the unused board files at the beginning of
> 2023, and I'd like to plan ahead for other hardware and feature
> support that can be removed after the next stable kernel
> (linux-6.12).
>
> TL;DR: I think we can deprecate toolchain support for ARMv4
> (pre-thumb), iWMMXt, BE32 and OABI (-mabi=apcs-gnu) *if* that
> helps gcc-15, as we'll likely not need those any more after
> gcc-14 will be too old to build new kernels (ca. 2030).
>
> I hope we can keep reducing the number of non-DT board files a
> lot further, but I still expect this to take several more years
> before it is DT-only. Please reply here if you are using any
> of them so we can spare them once more.
All this (and what was below the quote) looks reasonable to me,
including Samsung S3C64xx and keeping support for RPi 1 (I was using it
till ~3 years ago).
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-01 8:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 17:29 [RFC} arm architecture board/feature deprecation timeline Arnd Bergmann
2024-07-31 19:13 ` Aaro Koskinen
2024-08-01 8:59 ` Arnd Bergmann
2024-08-01 18:23 ` Aaro Koskinen
2024-08-02 12:53 ` Arnd Bergmann
2024-08-05 7:58 ` Arnd Bergmann
2024-08-05 12:30 ` Tony Lindgren
2024-08-05 13:37 ` Arnd Bergmann
2024-08-01 8:04 ` Krzysztof Kozlowski [this message]
2024-08-01 14:15 ` Richard Earnshaw
2024-08-02 15:12 ` Arnd Bergmann
2024-08-02 23:04 ` Linus Walleij
2024-08-20 14:58 ` Richard Earnshaw
2024-08-20 16:33 ` Arnd Bergmann
2024-08-01 19:53 ` Linus Walleij
2024-08-02 14:52 ` Arnd Bergmann
2024-08-15 18:24 ` Matt Turner
2024-08-19 7:37 ` Arnd Bergmann
2024-08-15 19:53 ` jeremy
2024-08-19 9:17 ` Arnd Bergmann
2024-08-19 14:12 ` Arnd Bergmann
2024-08-19 14:23 ` Andrew Lunn
2024-08-19 14:34 ` Arnd Bergmann
2024-08-19 17:08 ` jeremy
2024-08-21 6:15 ` Alexander Dahl
2024-08-21 7:51 ` 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=f5e8b8ca-33c7-4725-b751-fc9d76959423@kernel.org \
--to=krzk@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=debian-arm@lists.debian.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=jeremy@jeremypeper.com \
--cc=jmkrzyszt@gmail.com \
--cc=kristoffer.ericson@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nico@fluxnic.net \
--cc=nikita.shubin@maquefel.me \
--cc=ramanara@nvidia.com \
--cc=richard.earnshaw@arm.com \
--cc=richard.sandiford@arm.com \
--cc=robert.jarzmik@free.fr \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tony@atomide.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