From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
f4bug@amsat.org
Subject: [PATCH v1 0/7] enabling RasperryPi 4 emulation - WIP state
Date: Mon, 4 Oct 2021 14:47:34 +0100 [thread overview]
Message-ID: <20211004134742.2044280-1-alex.bennee@linaro.org> (raw)
Hi Phillipe,
I needed to test some Xen things on a model I could debug so I took
the liberty of re-basing you patches from a 2 years ago. Most of the
changes involve dropping patches since merged and dealing with the
resultant merging fallout. The fix I posted on Friday for the
calculation of the ram base for kernel loading is included. Other
tweaks involve moving the location of peri_base to what is indicated
by the DTBs (I'm still not sure where the Linux addresses come from,
does it re-map the physical address space somewhere?).
My testing ended at getting Xen to boot up and at least echo some
stuff to the console:
./qemu-system-aarch64 -machine raspi4b -serial mon:stdio -kernel ~/lsrc/xen/xen-only.cross.arm64/xen/xen -append "dom0_mem=1G,max:1G loglvl=all guest_loglvl=all console=d
tuart dtuart=serial0 sync_console" -display none -dtb ./bcm2711-rpi-4-b.dtb
- UART enabled -
- Boot CPU booting -
- Current EL 00000008 -
- Initialize CPU -
- Turning on paging -
- Zero BSS -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000000000000 - 000000003bffffff
(XEN)
(XEN) MODULE[0]: 0000000000200000 - 000000000034d0c8 Xen
(XEN) MODULE[1]: 0000000008000000 - 000000000801cea4 Device Tree
(XEN) RESVD[0]: 0000000000000000 - 0000000000001000
(XEN)
(XEN)
(XEN) Command line: <NULL>
(XEN) Domain heap initialised
(XEN) Booting using Device Tree
(XEN) Platform: Raspberry Pi 4
(XEN) No dtuart path configured
(XEN) Bad console= option 'dtuart'
My next steps involve debugging Xen so I thought I'd post where I am
for the next person that wants to properly wire up the Pi4.
Alex Bennée (1):
hw/arm: fix the position of vcram for raspi
Philippe Mathieu-Daudé (6):
hw/misc/bcm2835_property: Add FIXME comment for uninitialized memory
hw/misc/bcm2835_property: Handle the 'domain state' property
hw/arm/bcm2835_peripherals: Map various BCM2711 blocks
hw/arm/bcm2836: Add the BCM2711 which uses a GICv2
hw/arm/bcm2838: Map the PCIe memory space
hw/arm/raspi: Add the Raspberry Pi 4B board
include/hw/arm/bcm2835_peripherals.h | 9 ++-
include/hw/arm/bcm2836.h | 3 +
include/hw/arm/raspi_platform.h | 14 +++++
hw/arm/bcm2835_peripherals.c | 38 +++++++++---
hw/arm/bcm2836.c | 89 ++++++++++++++++++++++++++++
hw/arm/raspi.c | 34 ++++++++---
hw/misc/bcm2835_property.c | 10 ++++
7 files changed, 179 insertions(+), 18 deletions(-)
--
2.30.2
next reply other threads:[~2021-10-04 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 13:47 Alex Bennée [this message]
2021-10-04 13:47 ` [PATCH v1 1/7] hw/misc/bcm2835_property: Add FIXME comment for uninitialized memory Alex Bennée
2021-10-04 13:47 ` [PATCH v1 2/7] hw/misc/bcm2835_property: Handle the 'domain state' property Alex Bennée
2021-10-04 13:47 ` [PATCH v1 3/7] hw/arm: fix the position of vcram for raspi Alex Bennée
2021-10-04 13:47 ` [PATCH v1 4/7] hw/arm/bcm2835_peripherals: Map various BCM2711 blocks Alex Bennée
2021-10-04 13:47 ` [PATCH v1 5/7] hw/arm/bcm2836: Add the BCM2711 which uses a GICv2 Alex Bennée
2021-10-04 15:43 ` Alex Bennée
2021-10-04 13:47 ` [PATCH v1 6/7] hw/arm/bcm2838: Map the PCIe memory space Alex Bennée
2021-10-04 13:47 ` [PATCH v1 7/7] hw/arm/raspi: Add the Raspberry Pi 4B board Alex Bennée
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=20211004134742.2044280-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--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).