linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/powerpc: Remove retired CPUs from list of supported CPUs
Date: Wed, 10 Jul 2024 20:50:41 +1000	[thread overview]
Message-ID: <877cdt5xmm.fsf@mail.lhotse> (raw)
In-Reply-To: <e33ba7b242a104259fbcf1a4d4bdb0f1d1db6882.1720539170.git.christophe.leroy@csgroup.eu>

Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> 601, power4, 401, 403, 405, e200 and IBM-A2 support was removed by
> by following commits:
> - Commit 8b14e1dff067 ("powerpc: Remove support for PowerPC 601")
> - Commit 471d7ff8b51b ("powerpc/64s: Remove POWER4 support")
> - Commit 1b5c0967ab8a ("powerpc/40x: Remove support for IBM 403GCX")
> - Commit 39c8bf2b3cc1 ("powerpc: Retire e200 core (mpc555x processor)")
> - Commit fb5a515704d7 ("powerpc: Remove platforms/wsp and associated
> pieces")

There was also: 468a33028edd ("powerpc: Drop support for pre-POWER4 cpus")

> Remove them from the list of supported CPUs.

The CPU families doc is not intended to be a list of supported CPUs,
it's more of a family tree which includes the currently supported CPUs.

Even when I first added it there were CPUs mentioned that weren't
supported. (I realise the paragraph at the top of the file doesn't make
that clear)

I don't mind removing cores that are unsupported and unconnected to
other things, eg. A2, e200 and the 40x.

But for 601 and the early POWER cores I'd rather we marked the
unsupported ones with an asterisk or something. That way the family tree
still connects and includes all the history, otherwise I think it risks
being confusing.

Or maybe we use a different box outline (~) for unsupported cores? eg:

   +~~~~~~~~~~~~~~+                 +~~~~~~~~~~~~~~~~+
   |  Old POWER   | --------------> | RS64 (threads) |
   +~~~~~~~~~~~~~~+                 +~~~~~~~~~~~~~~~~+
          |
          |
          v
   +~~~~~~~~~~~~~~+                 +----------------+      +------+
   |     601      | --------------> |      603       | ---> | e300 |
   +~~~~~~~~~~~~~~+                 +----------------+      +------+
          |                                 |
          |                                 |
          v                                 v
   +--------------+    +-----+      +----------------+      +-------+
   |     604      |    | 755 | <--- |    750 (G3)    | ---> | 750CX |
   +--------------+    +-----+      +----------------+      +-------+
          |                                 |                   |
          |                                 |                   |
          v                                 v                   v
   +~~~~~~~~~~~~~~+                 +----------------+      +-------+
   | 620 (64 bit) |                 |      7400      |      | 750CL |
   +~~~~~~~~~~~~~~+                 +----------------+      +-------+
          |                                 |                   |
          |                                 |                   |
          v                                 v                   v
   +~~~~~~~~~~~~~~+                 +----------------+      +-------+
   |  POWER3/630  |                 |      7410      |      | 750FX |
   +~~~~~~~~~~~~~~+                 +----------------+      +-------+


cheers

      reply	other threads:[~2024-07-10 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 15:34 [PATCH] Documentation/powerpc: Remove retired CPUs from list of supported CPUs Christophe Leroy
2024-07-10 10:50 ` Michael Ellerman [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=877cdt5xmm.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=christophe.leroy@csgroup.eu \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=npiggin@gmail.com \
    /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).