Explain how users can compose their pre-OS environment purely from
binaries they've built themselves.
Cc: Andrei Warkentin <andrei.warken...@intel.com>
Cc: Ard Biesheuvel <ardb+tianoc...@kernel.org>
Cc: Gerd Hoffmann <kra...@redhat.com>
Cc: Jiewen Yao <jiewen....@intel.com>
Cc: Jordan Justen <jordan.l.jus...@intel.com>
Cc: Sunil V L <suni...@ventanamicro.com>
Signed-off-by: Laszlo Ersek <ler...@redhat.com>
---
Notes:
rendered version:
https://github.com/lersek/edk2/tree/bring-your-own-opensbi/OvmfPkg/RiscVVirt#test-with-your-own-opensbi-binary
OvmfPkg/RiscVVirt/README.md | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/OvmfPkg/RiscVVirt/README.md b/OvmfPkg/RiscVVirt/README.md
index 8c3ac37b802a..dbb40bbe89b0 100644
--- a/OvmfPkg/RiscVVirt/README.md
+++ b/OvmfPkg/RiscVVirt/README.md
@@ -69,3 +69,20 @@ Below example shows how to boot openSUSE Tumbleweed E20.
-device virtio-net-pci,netdev=net0 \
-device virtio-blk-device,drive=hd0 \
-drive
file=openSUSE-Tumbleweed-RISC-V-E20-efi.riscv64.raw,format=raw,id=hd0
+
+## Test with your own OpenSBI binary
+Using the above QEMU command line, **RISCV_VIRT_CODE.fd** is launched by the
+OpenSBI binary that is bundled with QEMU. You can build your own OpenSBI binary
+as well:
+
+ OPENSBI_DIR=...
+ git clone https://github.com/riscv/opensbi.git $OPENSBI_DIR
+ make -C $OPENSBI_DIR \
+ -j $(getconf _NPROCESSORS_ONLN) \
+ CROSS_COMPILE=riscv64-linux-gnu- \
+ PLATFORM=generic
+
+then specify that binary for QEMU, with the following additional command line
+option:
+
+ -bios $OPENSBI_DIR/build/platform/generic/firmware/fw_dynamic.bin
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108397): https://edk2.groups.io/g/devel/message/108397
Mute This Topic: https://groups.io/mt/101216052/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe:
https://edk2.groups.io/g/devel/leave/9847357/21656/1706620634/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
