[RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms

Martin Kennedy hurricos at gmail.com
Sun Mar 5 05:35:08 AEDT 2023


On Sat, Mar 4, 2023 at 4:37 AM Pali Rohár <pali at kernel.org> wrote:
>
> On Saturday 04 March 2023 07:31:49 Christophe Leroy wrote:
> > Le 03/03/2023 à 20:41, Crystal Wood a écrit :
> > > On Fri, 2023-03-03 at 10:14 +0100, Arnd Bergmann wrote:
> > >> On Fri, Mar 3, 2023, at 02:04, Paul Gortmaker wrote:
> > >>> 01/03/2023 (Wed 14:23) Christophe Leroy wrote:
> > >>>> Le 28/02/2023 ?? 18:51, Arnd Bergmann a ??crit??:
> > >>>> Hope it clarifies how those reference boards are used.
> > >>>
> > >>> It was really useful input and gave an insight into how things get used.
> > >>>
> > >>> But let me put a slightly different slant on things.  If there is no
> > >>> maintainer for the platform/architecture/CPU, then where is the
> > >>> obligation for mainline to keep it up to date just for your company to
> > >>> use the code/BSP as a reference?
> > >>>
> > >>> Do they continue to do this for one more year, or three or ...  ???
> > >>> Does someone list themselves in MAINTAINERS for arch/powerpc/83xx ?
> > >> ...
> > >>>
> > >>> If you see change 0123abcdef breaks boot on your platform, you have a
> > >>> legit voice to gripe about it right then and there.  Don't wait!!!
> > >>
> > >> I think the answer here is that Christophe is already the only person
> > >> that does this, so he is the de-facto maintainer for ppc32 regardless
> > >> of whether he wants himself listed in the file or not:
> > >>
> > >> $ git log --no-merges --format="%an" v5.0.. arch/powerpc/platforms/[458e]* |
> > >> sort | uniq -c | sort -rn | grep -vw 1
> > >>       61 Christophe Leroy
> > >>       12 Michael Ellerman
> > >>       11 Thomas Gleixner
> > >>       11 Oliver O'Halloran
> > >>       11 Liang He
> > >>        7 Uwe Kleine-König
> > >>        6 Nick Child
> > >>        4 Rasmus Villemoes
> > >>        4 Randy Dunlap
> > >>        4 Mike Rapoport
> > >>        4 Julia Lawall
> > >>        4 Andy Shevchenko
> > >>        3 Xiaoming Ni
> > >>        3 Nicholas Piggin
> > >>        3 Marc Zyngier
> > >>        3 Christophe JAILLET
> > >>        3 Christoph Hellwig
> > >>        2 Paul Gortmaker
> > >>        2 Mathieu Malaterre
> > >>        2 Markus Elfring
> > >>        2 Jordan Niethe
> > >>        2 Dmitry Torokhov
> > >>        2 Arnd Bergmann
> > >>
> > >> Pretty much everyone else on the list above only did treewide
> > >> cleanups, dead code removal or compile-time fixes, while Christophe
> > >> is the one that fixed machine specific bugs and added new features.
> > >
> > > Speaking of that, I'd be fine with Christophe replacing me in the "LINUX FOR
> > > POWERPC EMBEDDED PPC83XX AND PPC85XX" entry, given that he's been way more
> > > involved than me lately.
> >
> > MPC83XX yes I can, I have MPC8321E Hardware, but PPC85XX I'm not sure. I
> > don't know much more than what I can experiment with QEMU.
> >
> > Maybe Pali for MPC85XX ?
> >
> > Christophe
>
> I have P2020 SMP HW (mpc85xx platform) which I use on daily usage. So yes, I can help.
>
> Martin Kennedy has other P1/P2 mpc85xx hardware and is working on Linux
> support for it. So maybe can be interested in this discussion. I'm CCing.

I have mpc85xx hardware, mostly access points adapted from the
P1020WLAN board, but I am frankly a hobbyist. I do my work under
OpenWrt, and I have no relationship with the manufacturers of these
devices.

I only catch regressions on my boards when changes are backported to
the LTS kernel OpenWrt uses (so, presently, 5.15).

Martin


More information about the Linuxppc-dev mailing list