linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Joakim Tjernlund" <Joakim.Tjernlund@infinera.com>,
	"Leo Li" <leoyang.li@nxp.com>,
	"Paul Gortmaker" <paul.gortmaker@windriver.com>
Cc: Scott Wood <oss@buserror.net>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms
Date: Tue, 28 Feb 2023 18:51:06 +0100	[thread overview]
Message-ID: <83565b97-8149-492e-8f22-e3722e659b98@app.fastmail.com> (raw)
In-Reply-To: <1b9d4d586ae7bb5cddbb97fbc9ec7de1c475afee.camel@infinera.com>

On Tue, Feb 28, 2023, at 11:03, Joakim Tjernlund wrote:
> On Mon, 2023-02-27 at 14:48 -0600, Li Yang wrote:
>> > > > 
>> > > > Here, we remove the MPC8548E-MDS[1], the MPC8360E-MDS[2], the
>> > > > MPC837xE-MDS[3], and the MPC832x-MDS[4] board support from the kernel.
>> > > > 
>> > > > There will still exist several e300 Freescale Reference Design System (RDS)
>> > > > boards[5] and mini-ITX boards[6] with support in the kernel.  While these
>> > > > were more of a COTS "ready to deploy" design more suited to hobbyists, it
>> > > > probably makes sense to consider removing these as well, based on age.
>> > > 
>> > > These boards are mass market boards that sold in larger amount and are much more likely to still be used.  We would suggest we keep them for now.
>
> Agreed, the RDS design is still used here.

Can you elaborate what the typical kernel upgrade schedule for
these boards?

Note that for the debate about dropping the machines from future
kernels, it does not really matter how many remaining users there
are or how many boards get sold. The only question is whether
someone is still planning to provide upgrades to kernels later
than linux-6.3 in the future.

It sounds like there are commercial requirements for validating
and distributing kernel upgrades (in addition to hobbyist uses), so
I would expect that whoever is paying for the upgrades has a clear
plan for how much longer they are going to do that, or at least
a some idea of how many of the previous LTS kernels (5.10, 5.15,
6.1) ended up actually getting shipped to users.

It may be worth pointing out that the official webpage for
the MPC8313ERDB board in the example only lists a hilariously
outdated BSP kernel based on a patched linux-2.6.23 release,
so maybe the marketing team can change that to point to the
latest validated LTS kernel instead.

     Arnd

  reply	other threads:[~2023-02-28 17:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 11:59 [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms Paul Gortmaker
2023-02-20 11:59 ` [PATCH 1/4] powerpc: drop MPC834x_MDS platform support Paul Gortmaker
2023-02-20 11:59 ` [PATCH 2/4] powerpc: drop MPC836x_MDS " Paul Gortmaker
2023-02-20 11:59 ` [PATCH 3/4] powerpc: drop MPC837x_MDS " Paul Gortmaker
2023-02-20 11:59 ` [PATCH 4/4] powerpc: drop MPC832x_MDS " Paul Gortmaker
2023-02-20 22:40 ` [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms Leo Li
2023-02-24 21:16 ` Leo Li
2023-02-25 16:50   ` Paul Gortmaker
2023-02-25 22:49     ` Arnd Bergmann
2023-02-27 20:42       ` Li Yang
2023-02-27 20:48     ` Li Yang
2023-02-28 10:03       ` Joakim Tjernlund
2023-02-28 17:51         ` Arnd Bergmann [this message]
2023-02-28 18:20           ` Li Yang
2023-03-01 14:23           ` Christophe Leroy
2023-03-01 14:45             ` Arnd Bergmann
2023-03-03  1:04             ` Paul Gortmaker
2023-03-03  9:14               ` Arnd Bergmann
2023-03-03 19:41                 ` Crystal Wood
2023-03-04  7:31                   ` Christophe Leroy
2023-03-04  9:37                     ` Pali Rohár
2023-03-04 18:35                       ` Martin Kennedy
2023-03-09 10:41                 ` Michael Ellerman
2023-02-25  7:40 ` Christophe Leroy
2023-02-25 16:20   ` Paul Gortmaker
2023-04-26 12:10 ` Michael Ellerman

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=83565b97-8149-492e-8f22-e3722e659b98@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=Joakim.Tjernlund@infinera.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=leoyang.li@nxp.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).