All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: buildroot@buildroot.org
Cc: Bin Meng <bmeng@tinylab.org>,
	Alistair Francis <alistair.francis@wdc.com>,
	Jan-Benedict Glaw <jbglaw@lug-owl.de>
Subject: [Buildroot] [PATCH 01/10] configs/hifive_unleashed: Update to use OpenSBI 1.2
Date: Tue, 27 Jun 2023 00:00:21 +0800	[thread overview]
Message-ID: <20230626160030.93063-2-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20230626160030.93063-1-bmeng.cn@gmail.com>

From: Bin Meng <bmeng@tinylab.org>

Since the rest of RISC-V boards have been switched to use OpenSBI
1.2, let's update hifive_unleashed to use OpenSBI 1.2 too.

Resolves: https://bugs.busybox.net/show_bug.cgi?id=15658
Signed-off-by: Bin Meng <bmeng@tinylab.org>
---

 configs/hifive_unleashed_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configs/hifive_unleashed_defconfig b/configs/hifive_unleashed_defconfig
index 2b6ee6c08e..0440b14ba5 100644
--- a/configs/hifive_unleashed_defconfig
+++ b/configs/hifive_unleashed_defconfig
@@ -38,7 +38,7 @@ BR2_LINUX_KERNEL_INSTALL_TARGET=y
 # Bootloader
 BR2_TARGET_OPENSBI=y
 BR2_TARGET_OPENSBI_CUSTOM_VERSION=y
-BR2_TARGET_OPENSBI_CUSTOM_VERSION_VALUE="0.9"
+BR2_TARGET_OPENSBI_CUSTOM_VERSION_VALUE="1.2"
 BR2_TARGET_OPENSBI_PLAT="generic"
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_CUSTOM_VERSION=y
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-06-26 16:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 16:00 [Buildroot] [PATCH 00/10] riscv: Various fixes and small enhancements Bin Meng
2023-06-26 16:00 ` Bin Meng [this message]
2023-06-26 16:00 ` [Buildroot] [PATCH 02/10] configs/hifive_unleashed: Update to use U-Boot v2023.04 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 03/10] configs/hifive_unleashed: Enable BR2_RISCV_ISA_CUSTOM_RVA explicitly Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 04/10] configs/beaglev_defconfig: " Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 05/10] arch/Config.in.riscv: Remove BR2_RISCV_ISA_CUSTOM_RVA from BR2_riscv_custom Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 06/10] configs: riscv: Drop BR2_TARGET_OPENSBI_CUSTOM_VERSION Bin Meng
2023-06-26 17:10   ` Yann E. MORIN
2023-06-27  2:11     ` Bin Meng
2023-06-27 20:39       ` Yann E. MORIN
2023-06-26 16:00 ` [Buildroot] [PATCH 07/10] boot/opensbi: Config.in: Cosmetic style fix Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 08/10] boot/opensbi: Bump to version 1.3 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 09/10] board/sifive: hifive-unleashed: Update rootfs offset Bin Meng
2023-06-26 17:12   ` Yann E. MORIN
2023-08-12 21:12   ` Thomas Petazzoni via buildroot
2023-06-26 16:00 ` [Buildroot] [PATCH 10/10] board/sifive: hifive-unleashed: Include QEMU instructions in readme.txt Bin Meng
2023-06-26 17:21   ` Yann E. MORIN
2023-06-27  0:32     ` Alistair Francis
2023-06-28 15:15       ` Bin Meng
2023-08-12 21:14   ` Thomas Petazzoni via buildroot
2023-06-26 17:04 ` [Buildroot] [PATCH 00/10] riscv: Various fixes and small enhancements Yann E. MORIN

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=20230626160030.93063-2-bmeng.cn@gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=bmeng@tinylab.org \
    --cc=buildroot@buildroot.org \
    --cc=jbglaw@lug-owl.de \
    /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.