From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>,
Nikita Shubin <nikita.shubin@maquefel.me>,
Lukasz Majewski <lukma@denx.de>,
H Hartley Sweeten <hsweeten@visionengravers.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
Krzysztof Kozlowski <krzk@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Krzysztof Halasa <khalasa@piap.pl>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Marek Vasut <marek.vasut@gmail.com>,
Lubomir Rintel <lkundrak@v3.sk>,
Hartley Sweeten <hsweeten@visionengravers.com>,
linux-omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Sekhar Nori <nsekhar@ti.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Lennert Buytenhek <kernel@wantstofly.org>,
Marc Zyngier <maz@kernel.org>,
Mauri Sandberg <maukka@ext.kapsi.fi>
Subject: Re: Scheduling (unused) board file removal for linux-6.x
Date: Sun, 03 Jul 2022 13:24:05 +0200 [thread overview]
Message-ID: <ba286beeecaa0f11fce3d90ac4904ca7df310c22.camel@gmail.com> (raw)
In-Reply-To: <CAK8P3a0QDgKfHxri0YOj_4nJdGOD9ALRdCseb2EmJ36S7FrBaQ@mail.gmail.com>
Hello Nikita, Lukasz, Hartley,
On Thu, 2022-06-30 at 09:42 +0200, Arnd Bergmann wrote:
> > > ep93xx
> > >
> > > These are still used, and the platform includes the only remaining two
> > > board files that were added after linux-3.0. DT support is probably
> > > doable now that common-clk works. Need information about which boards
> > > are important.
> >
> > I'm still maintaining/able to test CONFIG_MACH_EDB93XX (edb93xx.c).
>
> Noted, thanks! We'll leave them in for 2023 then.
>
> Any thoughts on long-term uses for the platform? Do you know of users
> of any products other than the reference boards that would justify doing
> a DT conversion, or do we just delete the platform another time?
what are your projections for EP93xx support?
I'm personally a bit pessimistic about DT conversion because existing partition
tables were already challenged by the kernel growth. It has at least grown
+60% with the same config since 2006. This makes me think that 2023 EOL for this
SoC might be feasible.
--
Alexander Sverdlin.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-03 11:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 20:42 Scheduling (unused) board file removal for linux-6.x Arnd Bergmann
2022-06-29 20:59 ` Alexander Sverdlin
2022-06-30 7:42 ` Arnd Bergmann
2022-07-03 11:24 ` Alexander Sverdlin [this message]
2022-07-03 16:11 ` Arnd Bergmann
2022-07-04 9:07 ` Nikita Shubin
2022-06-29 22:53 ` Rob Herring
2022-06-30 7:57 ` Arnd Bergmann
2022-06-30 6:59 ` Marc Zyngier
2022-06-30 7:10 ` Tony Lindgren
2022-06-30 7:10 ` Krzysztof Kozlowski
2022-06-30 9:08 ` Arnd Bergmann
2022-06-30 9:22 ` Krzysztof Kozlowski
2022-06-30 12:10 ` Arnd Bergmann
2022-06-30 17:00 ` Krzysztof Kozlowski
2022-07-01 2:05 ` Tomasz Figa
2022-06-30 9:39 ` Krzysztof Hałasa
2022-06-30 11:32 ` Linus Walleij
2022-07-01 10:21 ` Daniel Mack
2022-07-01 10:53 ` Arnd Bergmann
2022-07-01 11:26 ` Alexander Sverdlin
2022-07-01 11:43 ` Linus Walleij
2022-07-01 12:28 ` Arnd Bergmann
2022-07-02 9:47 ` Christoph Hellwig
2022-07-02 10:06 ` Arnd Bergmann
2022-07-03 7:13 ` Christoph Hellwig
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=ba286beeecaa0f11fce3d90ac4904ca7df310c22.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=alim.akhtar@samsung.com \
--cc=andrew@lunn.ch \
--cc=arnd@kernel.org \
--cc=brgl@bgdev.pl \
--cc=daniel@zonque.org \
--cc=gregory.clement@bootlin.com \
--cc=haojian.zhuang@gmail.com \
--cc=hsweeten@visionengravers.com \
--cc=kernel@wantstofly.org \
--cc=khalasa@piap.pl \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=lukma@denx.de \
--cc=marek.vasut@gmail.com \
--cc=maukka@ext.kapsi.fi \
--cc=maz@kernel.org \
--cc=nikita.shubin@maquefel.me \
--cc=nsekhar@ti.com \
--cc=rmk+kernel@armlinux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).