From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Luc Michel" <luc@lmichel.fr>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
"Esteban Bosse" <estebanbosse@gmail.com>,
qemu-arm@nongnu.org,
"Stewart Hildebrand" <Stewart.Hildebrand@dornerworks.com>,
"Johnny Sun" <psunjohnny@gmail.com>
Subject: [RFC PATCH v2 0/3] hw/arm: Add the Raspberry Pi 4B
Date: Sun, 18 Oct 2020 22:55:48 +0200 [thread overview]
Message-ID: <20201018205551.1537927-1-f4bug@amsat.org> (raw)
Still not complete as we need to implement more firmware properties.
However state good enough for review, or in case someone want to work
on it and improve it.
Since RFC v1:
- Rebased
- Used recommendations from Luc
https://www.mail-archive.com/qemu-devel@nongnu.org/msg642450.html
Based-on: <20201018203358.1530378-1-f4bug@amsat.org>
Philippe Mathieu-Daudé (3):
hw/arm/bcm2836: Add the ARMv8 BCM2838
hw/arm/raspi: Add the Raspberry Pi 4 model B
hw/arm/raspi: Remove unsupported raspi4 peripherals from device tree
include/hw/arm/bcm2836.h | 3 +
hw/arm/bcm2836.c | 179 +++++++++++++++++++++++++++++++++++++++
hw/arm/raspi.c | 55 ++++++++++++
hw/arm/trace-events | 2 +
4 files changed, 239 insertions(+)
--
2.26.2
next reply other threads:[~2020-10-18 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 20:55 Philippe Mathieu-Daudé [this message]
2020-10-18 20:55 ` [RFC PATCH v2 1/3] hw/arm/bcm2836: Add the ARMv8 BCM2838 Philippe Mathieu-Daudé
2020-10-18 20:55 ` [RFC PATCH v2 2/3] hw/arm/raspi: Add the Raspberry Pi 4 model B Philippe Mathieu-Daudé
2020-10-18 20:55 ` [NOTFORMERGE PATCH v2 3/3] hw/arm/raspi: Remove unsupported raspi4 peripherals from device tree 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=20201018205551.1537927-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=Andrew.Baumann@microsoft.com \
--cc=Stewart.Hildebrand@dornerworks.com \
--cc=estebanbosse@gmail.com \
--cc=luc@lmichel.fr \
--cc=peter.maydell@linaro.org \
--cc=psunjohnny@gmail.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).