From: Stafford Horne <shorne@gmail.com>
To: QEMU Development <qemu-devel@nongnu.org>
Cc: Stafford Horne <shorne@gmail.com>
Subject: [PATCH v2 0/4] OpenRISC Device Tree Support
Date: Thu, 10 Feb 2022 21:33:59 +0900 [thread overview]
Message-ID: <20220210123403.2059926-1-shorne@gmail.com> (raw)
Changes since v1:
- Fixed typos pointed out by Philippe
- Moved usage of machine state to patch 3/4
- added config dependency on FDT
This series adds device tree support for the OpenRISC SIM hardware.
The simulator will generate an FDT and pass it to the kernel.
For example:
qemu-system-or1k -cpu or1200 -M or1k-sim \
-kernel /home/shorne/work/linux/vmlinux \
-initrd /home/shorne/work/linux/initramfs.cpio.gz \
-serial mon:stdio -nographic -gdb tcp::10001 -m 32
Using the linux kernel or1ksim_defconfig we can remove the built-in
dts and the kernel will boot as expected. The real benefit here is
being able to specify an external initrd which qemu will load into
memory and the device tree will tell the kernel where to find it.
Stafford Horne (4):
hw/openrisc/openrisc_sim: Create machine state for or1ksim
hw/openrisc/openrisc_sim: Parameterize initialization
hw/openrisc/openrisc_sim; Add support for loading a device tree
hw/openrisc/openrisc_sim: Add support for initrd loading
configs/targets/or1k-softmmu.mak | 1 +
hw/openrisc/openrisc_sim.c | 261 +++++++++++++++++++++++++++++--
2 files changed, 248 insertions(+), 14 deletions(-)
--
2.31.1
next reply other threads:[~2022-02-10 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 12:33 Stafford Horne [this message]
2022-02-10 12:34 ` [PATCH v2 1/4] hw/openrisc/openrisc_sim: Create machine state for or1ksim Stafford Horne
2022-02-10 12:34 ` [PATCH v2 2/4] hw/openrisc/openrisc_sim: Parameterize initialization Stafford Horne
2022-02-10 12:34 ` [PATCH v2 3/4] hw/openrisc/openrisc_sim; Add support for loading a device tree Stafford Horne
2022-02-10 12:34 ` [PATCH v2 4/4] hw/openrisc/openrisc_sim: Add support for initrd loading Stafford Horne
2022-02-17 18:04 ` Peter Maydell
2022-02-17 21:17 ` Stafford Horne
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=20220210123403.2059926-1-shorne@gmail.com \
--to=shorne@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.