linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Leo Li <leoyang.li@nxp.com>
Cc: Pali Roh??r <pali@kernel.org>, Scott Wood <oss@buserror.net>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Paul Mackerras <paulus@samba.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH 0/4] Remove some e500/MPC85xx evaluation platforms
Date: Mon, 17 Apr 2023 11:00:02 -0400	[thread overview]
Message-ID: <ZD1e8ujPlrCeYiuo@windriver.com> (raw)
In-Reply-To: <AM0PR04MB628965937FB711C2DA3A20FF8F999@AM0PR04MB6289.eurprd04.prod.outlook.com>

[RE: [RFC PATCH 0/4] Remove some e500/MPC85xx evaluation platforms] On 14/04/2023 (Fri 23:29) Leo Li wrote:

> 
> 
> > -----Original Message-----
> > From: Michael Ellerman <mpe@ellerman.id.au>
> > Sent: Thursday, April 13, 2023 9:14 PM
> > To: Leo Li <leoyang.li@nxp.com>; Paul Gortmaker
> > <paul.gortmaker@windriver.com>
> > Cc: Scott Wood <oss@buserror.net>; Paul Mackerras <paulus@samba.org>;
> > Claudiu Manoil <claudiu.manoil@nxp.com>; linuxppc-dev@lists.ozlabs.org;
> > Pali Roh??r <pali@kernel.org>
> > Subject: Re: [RFC PATCH 0/4] Remove some e500/MPC85xx evaluation
> > platforms
> > 
> > Li Yang <leoyang.li@nxp.com> writes:
> > > On Tue, Feb 21, 2023 at 1:52???PM Paul Gortmaker
> > > <paul.gortmaker@windriver.com> wrote:
> > >>
> > >> [This RFC is proposed for v6.4 and hence is based off linux-next.]
> > >>
> > >> In a similar theme to the e300/MPC83xx evaluation platform
> > >> removal[1], this targets removal of some 13 --> 21 year old
> > >> e500/MPC85xx evaluation boards that were produced in limited numbers
> > >> and primarily made available to hardware/software developers to shape
> > their own boards and BSPs.
> > >
> > > These e500 platforms are similar to the e300 platforms that they are
> > > still being shipped, the targeting market probably caused it to have a
> > > longer life cycle.
> > >
> > ...
> > >
> > > The difference here from the e300 platforms is that MPC8540ADS,
> > > MPC8560ADS, MPC8548CDS, MPC8568-MDS are the only reference
> > platforms
> > > supplied by us for these SoCs.  We don't have a separation of
> > > evaluation platforms vs product-like platforms like we did later.
> > > That probably means even if they don't look like "hobbyist" friendly
> > > they are more likely to be still in use.
> > 
> > OK. But what is the chance anyone is booting upstream kernels on them?
> 
> We do still have these parts shipped, which means that there are definitely active users of these silicons.  But it is really hard to say how many of they are running latest upstream kernel.  IMO, if the nature of the application is critical it is likely they will need to update the kernel to get all the security fixes.  And the reference board will be helpful as a starting point when they update the kernel.

I think the right thing to do here with this series is to remove the
super ancient 20+ year old MPC8540ADS and MPC8560ADS; and leave the
slightly more modern ones for another day in the future.

I don't think anyone can realistically argue against that?

Paul.
--

> 
> > 
> > I assume no one at NXP is testing upstream on those boards?
> 
> To be frank they are not included in the routine tests carried out by the development team now which is not ideal to me.  But I think the support team are probably willing to help on issues with latest kernel when needed.
> 
> Regards,
> Leo

      reply	other threads:[~2023-04-17 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 19:46 [RFC PATCH 0/4] Remove some e500/MPC85xx evaluation platforms Paul Gortmaker
2023-02-21 19:46 ` [PATCH 1/4] powerpc: drop MPC8540_ADS and MPC8560_ADS platform support Paul Gortmaker
2023-02-21 19:46 ` [PATCH 2/4] powerpc: drop MPC85xx_CDS " Paul Gortmaker
2023-02-21 19:46 ` [PATCH 3/4] powerpc: drop MPC8568_MDS / P1021_MDS " Paul Gortmaker
2023-02-21 19:46 ` [PATCH 4/4] powerpc: remove orphaned MPC85xx kernel config fragments Paul Gortmaker
2023-02-21 20:03   ` Pali Rohár
2023-02-21 21:29     ` Paul Gortmaker
2023-02-21 21:49       ` Pali Rohár
2023-03-02 23:30         ` Crystal Wood
2023-03-03  0:25           ` Paul Gortmaker
2023-02-21 20:13 ` [RFC PATCH 0/4] Remove some e500/MPC85xx evaluation platforms Pali Rohár
2023-02-21 21:35   ` Paul Gortmaker
2023-02-21 22:00     ` Pali Rohár
2023-02-27 21:16 ` Li Yang
2023-04-14  2:13   ` Michael Ellerman
2023-04-14 23:29     ` Leo Li
2023-04-17 15:00       ` Paul Gortmaker [this message]

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=ZD1e8ujPlrCeYiuo@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=leoyang.li@nxp.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    --cc=pali@kernel.org \
    --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).