linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Scott Wood <oss@buserror.net>, Paul Mackerras <paulus@samba.org>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Li Yang <leoyang.li@nxp.com>
Subject: Re: [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms
Date: Sat, 25 Feb 2023 11:20:12 -0500	[thread overview]
Message-ID: <Y/o1PDFnLr/cdXHk@windriver.com> (raw)
In-Reply-To: <211175b3-bae9-4f66-8532-fe48c6421180@csgroup.eu>

[Re: [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms] On 25/02/2023 (Sat 07:40) Christophe Leroy wrote:

> 
> 
> Le 20/02/2023 ?? 12:59, Paul Gortmaker a ??crit??:
> > [This RFC is proposed for v6.4 and hence is based off linux-next.]
> > 
> > This series removes support for four e300 (MPC83xx) Freescale processor
> > family evaluation boards that were added to the kernel in the 2006 era.
> > 
> > These boards were all of a very similar form factor, a largish PCI or PCI-X
> > card that could also be used standalone with an external power brick, and
> > all shared the Modular Development System (MDS) designation.
> > 
> > These platforms were made in limited quantity and were generally designed
> > to get early silicon into the hands of OEMs who would later develop their
> > own boards/platforms.  As such, availability was limited to those who would
> > be working on boards and/or BSP support.
> > 
> > Many early revision MDS platforms used a mechanical clamping system to hold
> > the BGA CPU in place to facilitate CPU updates -- something not normally
> > possible for a soldered down BGA in a COTS system.
> > 
> > The point of these details is to give context that reflects that these four
> > boards were made in limited quantities, were not in a form factor that is
> > really "hobbyist" friendly and hence make sense for removal 17 years later.
> > 
> > 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.
> 
> Those boards are still being sold, see 
> https://www.components-store.fr/product/NXP-Semiconductors-Freescale/MPC8323E-RDB.html 
> they have 4600 pieces in stock.

Just to clarify for others - your link is for RDB boards - which I said
should be considered, but are not touched in this series.

Secondly, even if there may exist a large amount of NOS (New Old Stock)
of RDB boards from 15+ years ago - the reality is that they will only be
used in small quantities to repair legacy STB or similar - where no
hardware upgrade path exists.  That corner case will happen w/o changing
firmware or software (i.e. u-boot or kernel).

I can assure you that no sane company is going to take a 2006 STB/PVR
and do a software update to a 6.4 kernel.  That would go against decades
of Product Life Cycle experience, and would be inviting disaster as you
go up the wrong side of the bathtub curve.

As for hobbyists - feel free to go ahead and e-mail the folks at your
components-store link and ask for a quote, since they don't list a
price.  When you get an answer of $800-$2000 USD - tell me who is going
buy one vs. a modern PC.  Oh, and ask if they have next day shipping,
since they claim to have 4600 in stock - which also seems very suspect,
or a horribly bad investment on their part.

Don't get me wrong - I appreciate the input, but I don't think it really
alters what the right thing to do is for the 6.4+ kernel.

Thanks,
Paul.
--

> 
> Christophe

  reply	other threads:[~2023-02-25 16:21 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
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 [this message]
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=Y/o1PDFnLr/cdXHk@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=claudiu.manoil@nxp.com \
    --cc=leoyang.li@nxp.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    --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).