linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nikita Shubin <nikita.shubin@maquefel.me>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	Lukasz Majewski <lukma@denx.de>,
	H Hartley Sweeten <hsweeten@visionengravers.com>,
	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>,
	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: Mon, 4 Jul 2022 12:07:49 +0300	[thread overview]
Message-ID: <20220704120749.7a742c2c@redslave.neermore.group> (raw)
In-Reply-To: <CAK8P3a1ZhFiPPR=tkLgsMB8pFjFoqiuD9GacTWBn0KM4nNynNQ@mail.gmail.com>

Hello Arnd and Alexander!

On Sun, 3 Jul 2022 18:11:36 +0200
Arnd Bergmann <arnd@kernel.org> wrote:

> On Sun, Jul 3, 2022 at 1:24 PM Alexander Sverdlin
> <alexander.sverdlin@gmail.com> wrote:
> > 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.  
> 
> I don't think converting the platform to DT will make the space
> problem noticeably
> worse, as the DT infrastructure is already enabled unconditionally
> since the multiplatform enablement. There are probably a few more
> lines that need to be added to parse DT properties in a couple of
> drivers, but removing the board files
> will save a bit as well.
> 
> There is little hope of stopping the general accumulation of code
> bloat through, so any boards that are hitting a size limit are
> probably at the end of their lives
> regardless.
> 
>          Arnd

On the bright side i have a working (bootable with UBIFS rootfs)
dt-based version of ts7250. Did almost a year ago, but unfortunately
got caught by RISC-V bustle, Sorry for github links:

Almost "clean" branch:
https://github.com/maquefel/linux/tree/ep93xx_dt_rework 

Dirty, last known good branch:
https://github.com/maquefel/linux/tree/gpio/devel-ep93xx-rework-v6

But all my users moved from ts7250 usage to other products, so i am
okay if it vanishes from main tree...

I have a dozen of ts7250, even with TS-DIO24, TS-SER4, CAN etc..., if
someone is interested in Device Tree version of ep93xx/ts7250, it's not
a problem for me to finalize the current work on the top of most recent
version, but i can test only on ts7250.

Yours,
Nikita Shubin.









_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-07-04  9:09 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
2022-07-03 16:11       ` Arnd Bergmann
2022-07-04  9:07         ` Nikita Shubin [this message]
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=20220704120749.7a742c2c@redslave.neermore.group \
    --to=nikita.shubin@maquefel.me \
    --cc=aaro.koskinen@iki.fi \
    --cc=alexander.sverdlin@gmail.com \
    --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=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).