[Buildroot] [PATCH 06/10] configs: riscv: Drop BR2_TARGET_OPENSBI_CUSTOM_VERSION

Yann E. MORIN yann.morin.1998 at free.fr
Tue Jun 27 20:39:36 UTC 2023


Bin, All,

On 2023-06-27 10:11 +0800, Bin Meng spake thusly:
> On Tue, Jun 27, 2023 at 1:10 AM Yann E. MORIN <yann.morin.1998 at free.fr> wrote:
> > On 2023-06-27 00:00 +0800, Bin Meng spake thusly:
> > > From: Bin Meng <bmeng at tinylab.org>
> > > Since commit 64f1f82385b2 ("boot/opensbi: Bump to version 1.2"),
> > > the default OpenSBI version has been bumped up to 1.2. With that,
> > > there is no need to define a custom version in each RISC-V board's
> > > defconfig files.
> > In fact, no, because opensbi is a "critical" component part of the boot
> > chain and, like uboot or the kernel, we want to pin the version we use
> > in defconfig files. We only want the v ersion to be bumped in defconfig,
> > when someone actually tested the defconfig still generates a bootable
> > system.
> Makes sense to me.
> But I would argue at least we should update
> qemu_riscv32_virt_defconfig and qemu_riscv64_virt_defconfig to use the
> latest OpenSBI due to the reason that:
> 1. they are the main platforms to develop and test OpenSBI
> 2. latest OpenSBI binaries will always be integrated into QEMU as the
> default bios
> thoughts?

For the qemu defconfigs, I wouild indeed understand that we use the
latest version; the rationale looks sound.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



More information about the buildroot mailing list