From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Mark Corbin <mark@dibsco.co.uk>, Romain Naour <romain.naour@gmail.com>
Subject: [Buildroot] [PATCH 2/4] configs/qemu_riscv64_virt_defconfig: use OpenSBI 1.2
Date: Sat, 7 Jan 2023 09:27:07 +0100 [thread overview]
Message-ID: <20230107082710.2609784-2-peter@korsgaard.com> (raw)
In-Reply-To: <20230107082710.2609784-1-peter@korsgaard.com>
Rather than the default (currently 0.9).
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
configs/qemu_riscv64_virt_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/configs/qemu_riscv64_virt_defconfig b/configs/qemu_riscv64_virt_defconfig
index c455680ee0..b3174a152c 100644
--- a/configs/qemu_riscv64_virt_defconfig
+++ b/configs/qemu_riscv64_virt_defconfig
@@ -25,6 +25,8 @@ BR2_LINUX_KERNEL_IMAGE=y
# Bootloader
BR2_TARGET_OPENSBI=y
+BR2_TARGET_OPENSBI_CUSTOM_VERSION=y
+BR2_TARGET_OPENSBI_CUSTOM_VERSION_VALUE="1.2"
BR2_TARGET_OPENSBI_PLAT="generic"
# host-qemu for gitlab testing
--
2.30.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-01-07 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 8:27 [Buildroot] [PATCH 1/4] configs/qemu_riscv32_virt_defconfig: use OpenSBI 1.2 Peter Korsgaard
2023-01-07 8:27 ` Peter Korsgaard [this message]
2023-01-07 19:25 ` [Buildroot] [PATCH 2/4] configs/qemu_riscv64_virt_defconfig: " Peter Korsgaard
2023-01-07 8:27 ` [Buildroot] [PATCH 3/4] configs/spike_riscv64_defconfig: " Peter Korsgaard
2023-01-07 11:01 ` Julien Olivain
2023-01-07 19:25 ` Peter Korsgaard
2023-01-07 8:27 ` [Buildroot] [PATCH 4/4] configs/hifive_unleashed_defconfig: explicitly use OpenSBI 0.9 Peter Korsgaard
2023-01-07 8:40 ` Peter Korsgaard
2023-01-07 19:25 ` Peter Korsgaard
2023-01-07 19:25 ` [Buildroot] [PATCH 1/4] configs/qemu_riscv32_virt_defconfig: use OpenSBI 1.2 Peter Korsgaard
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=20230107082710.2609784-2-peter@korsgaard.com \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=mark@dibsco.co.uk \
--cc=romain.naour@gmail.com \
/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