From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Cédric Le Goater" <clg@redhat.com>, qemu-devel@nongnu.org
Cc: <qemu-ppc@nongnu.org>, "Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v2] ppc: Deprecate 'ref405ep' machine and 405 CPUs
Date: Wed, 08 May 2024 22:30:57 +1000 [thread overview]
Message-ID: <D149JDYPG4NB.GTUPG8F1OZL2@gmail.com> (raw)
In-Reply-To: <20240507123332.641708-1-clg@redhat.com>
On Tue May 7, 2024 at 10:33 PM AEST, Cédric Le Goater wrote:
> The 'ref405ep' machine and PPC 405 CPU have no known users, firmware
> images are not available, OpenWRT dropped support in 2019, U-Boot in
> 2017, Linux also is dropping support in 2024. It is time to let go of
> this ancient hardware and focus on newer CPUs and platforms.
>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
Acked-by: Nicholas Piggin <npiggin@gmail.com>
> ---
> v2: fixed header line
>
> docs/about/deprecated.rst | 8 ++++++++
> hw/ppc/ppc405_boards.c | 1 +
> 2 files changed, 9 insertions(+)
>
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index 03f8b1b655e071432ecd9decf61e194821d06928..e22acb17f296362509a3e143ba61bafd210a6c91 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -258,6 +258,14 @@ dropping the ``cheetah`` OMAP1 board, because we don't have any
> test images for it and don't know of anybody who does; the ``sx1``
> and ``sx1-v1`` OMAP1 machines remain supported for now.
>
> +PPC 405 ``ref405ep`` machine (since 9.1)
> +''''''''''''''''''''''''''''''''''''''''
> +
> +The ``ref405ep`` machine and PPC 405 CPU have no known users, firmware
> +images are not available, OpenWRT dropped support in 2019, U-Boot in
> +2017, Linux also is dropping support in 2024. It is time to let go of
> +this ancient hardware and focus on newer CPUs and platforms.
> +
> Backend options
> ---------------
>
> diff --git a/hw/ppc/ppc405_boards.c b/hw/ppc/ppc405_boards.c
> index 4092ebc1ab59de14b66ebad2be7eb019faf45db1..c44e7ed162fae5ec884ba4e458138f84430a8460 100644
> --- a/hw/ppc/ppc405_boards.c
> +++ b/hw/ppc/ppc405_boards.c
> @@ -350,6 +350,7 @@ static void ppc405_machine_class_init(ObjectClass *oc, void *data)
> mc->init = ppc405_init;
> mc->default_ram_size = 128 * MiB;
> mc->default_ram_id = "ppc405.ram";
> + mc->deprecation_reason = "machine is old and unmaintained";
> }
>
> static const TypeInfo ppc405_machine_type = {
next prev parent reply other threads:[~2024-05-08 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 12:33 [PATCH v2] ppc: Deprecate 'ref405ep' machine and 405 CPUs Cédric Le Goater
2024-05-08 12:30 ` Nicholas Piggin [this message]
2024-05-08 21:17 ` Philippe Mathieu-Daudé
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=D149JDYPG4NB.GTUPG8F1OZL2@gmail.com \
--to=npiggin@gmail.com \
--cc=clg@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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).