linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <linuxppc-dev@lists.ozlabs.org>
Cc: Li Yang <leoyang.li@nxp.com>, Scott Wood <oss@buserror.net>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Paul Mackerras <paulus@samba.org>
Subject: [RFC PATCH 0/4] Remove some e300/MPC83xx evaluation platforms
Date: Mon, 20 Feb 2023 06:59:09 -0500	[thread overview]
Message-ID: <20230220115913.25811-1-paul.gortmaker@windriver.com> (raw)

[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.

But before we get to that, lets see how this goes -- and then we should
look at similar early e500 evaluation platforms [MPC8540-ADS, etc] next,
as the oldest there date back to 2002[7] -- before considering RDB/mITX.

I intentionally didn't put any links in the commits, since as we all know,
they tend not to be stable long term, so keep them here in the merge data.
Credit to NXP for keeping around these old legacy docs this long!

Paul.

--

[1] https://www.nxp.com/design/qoriq-developer-resources/mpc8349e-modular-development-system:MPC8349EMDS
[2] https://www.nxp.com/docs/en/user-guide/MPC8360EMDSUM.pdf
[3] https://www.nxp.com/products/processors-and-microcontrollers/legacy-mpu-mcus/powerquicc-processors/powerquicc-iii-mpc85xx/mpc837xe-modular-development-system:MPC837XEMDS
[4] https://www.nxp.com/products/processors-and-microcontrollers/legacy-mpu-mcus/powerquicc-processors/powerquicc-ii-pro-mpc83xx/low-power-powerquicc-ii-pro-processor-with-ddr2-tdm-pci-security-usb-quicc-engine-with-utopia:MPC8323E
[5] https://www.nxp.com/docs/en/fact-sheet/MPC8379ERDBFS.pdf
[6] https://www.digikey.ca/en/products/detail/nxp-usa-inc/MPC8349E-MITX-GP/1204733
[7] https://www.nxp.com/docs/en/reference-manual/MPC8560ADSUG.pdf

Cc: Scott Wood <oss@buserror.net>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Li Yang <leoyang.li@nxp.com>
Cc: Claudiu Manoil <claudiu.manoil@nxp.com>

---

Paul Gortmaker (4):
  powerpc: drop MPC834x_MDS platform support
  powerpc: drop MPC836x_MDS platform support
  powerpc: drop MPC837x_MDS platform support
  powerpc: drop MPC832x_MDS platform support

 arch/powerpc/boot/Makefile                    |   1 -
 arch/powerpc/boot/dts/mpc832x_mds.dts         | 436 ---------------
 arch/powerpc/boot/dts/mpc834x_mds.dts         | 403 --------------
 arch/powerpc/boot/dts/mpc836x_mds.dts         | 481 -----------------
 arch/powerpc/boot/dts/mpc8377_mds.dts         | 505 ------------------
 arch/powerpc/boot/dts/mpc8378_mds.dts         | 489 -----------------
 arch/powerpc/boot/dts/mpc8379_mds.dts         | 455 ----------------
 .../configs/83xx/mpc832x_mds_defconfig        |  59 --
 .../configs/83xx/mpc834x_mds_defconfig        |  58 --
 .../configs/83xx/mpc836x_mds_defconfig        |  64 ---
 .../configs/83xx/mpc837x_mds_defconfig        |  58 --
 arch/powerpc/configs/mpc83xx_defconfig        |   4 -
 arch/powerpc/configs/ppc6xx_defconfig         |   4 -
 arch/powerpc/platforms/83xx/Kconfig           |  32 --
 arch/powerpc/platforms/83xx/Makefile          |   4 -
 arch/powerpc/platforms/83xx/mpc832x_mds.c     | 110 ----
 arch/powerpc/platforms/83xx/mpc834x_mds.c     | 101 ----
 arch/powerpc/platforms/83xx/mpc836x_mds.c     | 210 --------
 arch/powerpc/platforms/83xx/mpc837x_mds.c     | 103 ----
 19 files changed, 3577 deletions(-)
 delete mode 100644 arch/powerpc/boot/dts/mpc832x_mds.dts
 delete mode 100644 arch/powerpc/boot/dts/mpc834x_mds.dts
 delete mode 100644 arch/powerpc/boot/dts/mpc836x_mds.dts
 delete mode 100644 arch/powerpc/boot/dts/mpc8377_mds.dts
 delete mode 100644 arch/powerpc/boot/dts/mpc8378_mds.dts
 delete mode 100644 arch/powerpc/boot/dts/mpc8379_mds.dts
 delete mode 100644 arch/powerpc/configs/83xx/mpc832x_mds_defconfig
 delete mode 100644 arch/powerpc/configs/83xx/mpc834x_mds_defconfig
 delete mode 100644 arch/powerpc/configs/83xx/mpc836x_mds_defconfig
 delete mode 100644 arch/powerpc/configs/83xx/mpc837x_mds_defconfig
 delete mode 100644 arch/powerpc/platforms/83xx/mpc832x_mds.c
 delete mode 100644 arch/powerpc/platforms/83xx/mpc834x_mds.c
 delete mode 100644 arch/powerpc/platforms/83xx/mpc836x_mds.c
 delete mode 100644 arch/powerpc/platforms/83xx/mpc837x_mds.c

-- 
2.17.1


             reply	other threads:[~2023-02-20 12:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 11:59 Paul Gortmaker [this message]
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
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=20230220115913.25811-1-paul.gortmaker@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=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).