From: Bin Meng <bmeng.cn@gmail.com>
To: Alistair Francis <Alistair.Francis@wdc.com>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: [PATCH 2/2] riscv: sifive_u: Update BIOS_FILENAME for 32-bit
Date: Thu, 20 Feb 2020 06:42:38 -0800 [thread overview]
Message-ID: <1582209758-2996-2-git-send-email-bmeng.cn@gmail.com> (raw)
In-Reply-To: <1582209758-2996-1-git-send-email-bmeng.cn@gmail.com>
Update BIOS_FILENAME to consider 32-bit bios image file name.
Tested booting Linux v5.5 32-bit image (built from rv32_defconfig
plus CONFIG_SOC_SIFIVE) with the default 32-bit bios image.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
---
hw/riscv/sifive_u.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/hw/riscv/sifive_u.c b/hw/riscv/sifive_u.c
index ca561d3..371133e 100644
--- a/hw/riscv/sifive_u.c
+++ b/hw/riscv/sifive_u.c
@@ -57,7 +57,11 @@
#include <libfdt.h>
-#define BIOS_FILENAME "opensbi-riscv64-sifive_u-fw_jump.bin"
+#if defined(TARGET_RISCV32)
+# define BIOS_FILENAME "opensbi-riscv32-sifive_u-fw_jump.bin"
+#else
+# define BIOS_FILENAME "opensbi-riscv64-sifive_u-fw_jump.bin"
+#endif
static const struct MemmapEntry {
hwaddr base;
--
2.7.4
next prev parent reply other threads:[~2020-02-20 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 14:42 [PATCH 1/2] riscv: roms: Add 32-bit OpenSBI firmware image for sifive_u Bin Meng
2020-02-20 14:42 ` Bin Meng [this message]
2020-02-21 19:51 ` [PATCH 2/2] riscv: sifive_u: Update BIOS_FILENAME for 32-bit Alistair Francis
2020-02-21 19:51 ` Alistair Francis
2020-02-22 2:52 ` Bin Meng
2020-02-22 2:52 ` Bin Meng
2020-02-22 3:55 ` Alistair Francis
2020-02-22 3:55 ` Alistair Francis
2020-02-20 17:31 ` [PATCH 1/2] riscv: roms: Add 32-bit OpenSBI firmware image for sifive_u Philippe Mathieu-Daudé
2020-02-21 2:38 ` Bin Meng
2020-02-21 2:38 ` Bin Meng
2020-02-21 5:54 ` Anup Patel
2020-02-21 5:54 ` Anup Patel
2020-02-21 8:54 ` Philippe Mathieu-Daudé
2020-02-22 14:53 ` Bin Meng
2020-02-22 14:53 ` Bin Meng
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=1582209758-2996-2-git-send-email-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmerdabbelt@google.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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.