From: Peter Maydell <peter.maydell@linaro.org>
To: Sergey Kambalin <serg.oker@gmail.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
"Sergey Kambalin" <sergey.kambalin@auriga.com>,
"Phil Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v6 00/41] Raspberry Pi 4B machine
Date: Tue, 27 Feb 2024 11:26:55 +0000 [thread overview]
Message-ID: <CAFEAcA_An-KUbaKHDGmk7Uiovft-8JDbW9J1s36wccS2sh9vJg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_brkckzDZh_-UJ-KFfBGvjPozPHNmG-bWFO0Xa63R0Gg@mail.gmail.com>
On Mon, 26 Feb 2024 at 18:09, Peter Maydell <peter.maydell@linaro.org> wrote:
> I think the one question I have left is the name of the
> board: currently it's "raspi4b-2g", but should we name
> it just "raspi4b"? None of the names we use for the other
> raspi boards we model have a suffix like the "-2g" here.
> Philippe, do you have an opinion here ?
I had a look at what the different raspi4 models are, and
it looks like they're all the same except for the amount
of RAM. For QEMU, if we wanted to allow users to pick
the RAM size we'd do it via the -m option, not by using
different model names. So I think on that basis and to
match the existing raspi machine names, we should call
this simply "raspi4b". So I'll make that name change in the
patches I have in target-arm.next.
thanks
-- PMM
next prev parent reply other threads:[~2024-02-27 11:28 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 0:02 [PATCH v6 00/41] Raspberry Pi 4B machine Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 01/41] Split out common part of BCM283X classes Sergey Kambalin
2024-02-27 8:45 ` Philippe Mathieu-Daudé
2024-02-26 0:02 ` [PATCH v6 02/41] Split out common part of peripherals Sergey Kambalin
2024-02-27 8:58 ` Philippe Mathieu-Daudé
2024-02-26 0:02 ` [PATCH v6 03/41] Split out raspi machine common part Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 04/41] Introduce BCM2838 SoC Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 05/41] Add GIC-400 to " Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 06/41] Add BCM2838 GPIO stub Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 07/41] Implement BCM2838 GPIO functionality Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 08/41] Connect SD controller to BCM2838 GPIO Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 09/41] Add GPIO and SD to BCM2838 periph Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 10/41] Introduce Raspberry PI 4 machine Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 11/41] Temporarily disable unimplemented rpi4b devices Sergey Kambalin
2024-02-26 13:35 ` Philippe Mathieu-Daudé
2024-02-26 13:39 ` Peter Maydell
2024-02-26 16:06 ` Philippe Mathieu-Daudé
2024-02-26 16:41 ` Peter Maydell
2024-02-27 4:54 ` Kambalin, Sergey
2024-02-26 0:02 ` [PATCH v6 12/41] Add memory region for BCM2837 RPiVid ASB Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 13/41] Add BCM2838 PCIE Root Complex Sergey Kambalin
2024-02-26 13:25 ` Philippe Mathieu-Daudé
2024-02-26 0:02 ` [PATCH v6 14/41] Add BCM2838 PCIE host Sergey Kambalin
2024-02-26 16:28 ` Philippe Mathieu-Daudé
2024-02-26 0:02 ` [PATCH v6 15/41] Enable BCM2838 PCIE Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 16/41] Add RPi4 RNG200 Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 17/41] Implement BCM2838 thermal sensor Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 18/41] Add clock_isp stub Sergey Kambalin
2024-02-26 16:06 ` Philippe Mathieu-Daudé
2024-02-26 16:19 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 19/41] Add GENET stub Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 20/41] Add GENET register structs. Part 1 Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 21/41] Add GENET register structs. Part 2 Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 22/41] Add GENET register structs. Part 3 Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 23/41] Add GENET register structs. Part 4 Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 24/41] Add GENET register access macros Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 25/41] Implement GENET register ops Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 26/41] Implement GENET MDIO Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 27/41] Implement GENET TX path Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 28/41] Implement GENET RX path Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 29/41] Enable BCM2838 GENET controller Sergey Kambalin
2024-02-26 0:02 ` [PATCH v6 30/41] Add Rpi4b boot tests Sergey Kambalin
2024-02-26 16:40 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 31/41] Add mailbox test stub Sergey Kambalin
2024-02-26 16:21 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 32/41] Add mailbox test constants Sergey Kambalin
2024-02-26 16:23 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 33/41] Add mailbox tests tags. Part 1 Sergey Kambalin
2024-02-26 16:23 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 34/41] Add mailbox tests tags. Part 2 Sergey Kambalin
2024-02-26 16:23 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 35/41] Add mailbox tests tags. Part 3 Sergey Kambalin
2024-02-26 16:24 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 36/41] Add mailbox property tests. Part 1 Sergey Kambalin
2024-02-26 16:24 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 37/41] Add mailbox property tests. Part 2 Sergey Kambalin
2024-02-26 16:24 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 38/41] Add mailbox property tests. Part 3 Sergey Kambalin
2024-02-26 16:24 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 39/41] Add missed BCM2835 properties Sergey Kambalin
2024-02-26 16:25 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 40/41] Append added properties to mailbox test Sergey Kambalin
2024-02-26 16:25 ` Peter Maydell
2024-02-26 0:02 ` [PATCH v6 41/41] Add RPi4B to raspi.rst Sergey Kambalin
2024-02-26 16:42 ` Peter Maydell
2024-02-26 16:43 ` Peter Maydell
2024-02-26 16:52 ` Philippe Mathieu-Daudé
2024-02-26 16:54 ` Peter Maydell
2024-02-26 18:09 ` [PATCH v6 00/41] Raspberry Pi 4B machine Peter Maydell
2024-02-27 11:26 ` Peter Maydell [this message]
2024-02-27 15:22 ` Peter Maydell
2024-02-27 17:25 ` Peter Maydell
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=CAFEAcA_An-KUbaKHDGmk7Uiovft-8JDbW9J1s36wccS2sh9vJg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=serg.oker@gmail.com \
--cc=sergey.kambalin@auriga.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).