qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Peter Krempa" <pkrempa@redhat.com>,
	libvir-list@redhat.com,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
	"Andrew Jeffery" <andrew@aj.id.au>,
	qemu-arm@nongnu.org, "Joel Stanley" <joel@jms.id.au>,
	"Cédric Le Goater" <clg@kaod.org>
Subject: [PATCH-for-5.2 1/4] docs/system: Deprecate raspi2/raspi3 machine aliases
Date: Fri, 20 Nov 2020 16:21:37 +0100	[thread overview]
Message-ID: <20201120152140.2493197-2-f4bug@amsat.org> (raw)
In-Reply-To: <20201120152140.2493197-1-f4bug@amsat.org>

Since commit aa35ec2213b ("hw/arm/raspi: Use more specific
machine names") the raspi2/raspi3 machines have been renamed
as raspi2b/raspi3b.

Note, rather than the raspi3b, the raspi3ap introduced in
commit 5be94252d34 ("hw/arm/raspi: Add the Raspberry Pi 3
model A+") is a closer match to what QEMU models, but only
provides 512 MB of RAM.

As more Raspberry Pi 2/3 models are emulated, in order
to avoid confusion, deprecate the raspi2/raspi3 machine
aliases.

ACKed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
 docs/system/deprecated.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst
index d98464098f5..d1bc03d7e61 100644
--- a/docs/system/deprecated.rst
+++ b/docs/system/deprecated.rst
@@ -346,6 +346,13 @@ This machine has been renamed ``fuloong2e``.
 These machine types are very old and likely can not be used for live migration
 from old QEMU versions anymore. A newer machine type should be used instead.
 
+Raspberry Pi ``raspi2`` and ``raspi3`` machines (since 5.2)
+'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
+
+The Raspberry Pi machines come in various models (A, A+, B, B+). To be able
+to distinct which model is used, the ``raspi2`` and ``raspi3`` machines  have
+been respectively renamed ``raspi2b`` and ``raspi3b``.
+
 Device options
 --------------
 
-- 
2.26.2



  reply	other threads:[~2020-11-20 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 15:21 [PATCH-for-5.2 0/4] docs/system/arm: Document raspi/tosa boards Philippe Mathieu-Daudé
2020-11-20 15:21 ` Philippe Mathieu-Daudé [this message]
2020-11-20 16:46   ` [PATCH-for-5.2 1/4] docs/system: Deprecate raspi2/raspi3 machine aliases Peter Maydell
2020-11-20 15:21 ` [PATCH-for-5.2 2/4] docs/system/arm: Document the various raspi boards Philippe Mathieu-Daudé
2020-11-20 15:24   ` Philippe Mathieu-Daudé
2020-11-20 16:48   ` Peter Maydell
2020-11-20 17:09     ` Philippe Mathieu-Daudé
2020-11-20 15:21 ` [PATCH-for-5.2 3/4] docs/system/arm: Document OpenPOWER Witherspoon BMC model Front LEDs Philippe Mathieu-Daudé
2020-11-20 16:17   ` Cédric Le Goater
2020-11-20 15:21 ` [RFC PATCH-for-5.2 4/4] docs/system/arm: Document the Sharp Zaurus SL-6000 Philippe Mathieu-Daudé
2020-11-20 16:52   ` Peter Maydell
2020-11-20 17:11     ` 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=20201120152140.2493197-2-f4bug@amsat.org \
    --to=f4bug@amsat.org \
    --cc=Andrew.Baumann@microsoft.com \
    --cc=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=joel@jms.id.au \
    --cc=libvir-list@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pkrempa@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.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).