Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Liang via buildroot <buildroot@buildroot.org>
To: Vincent Jardin <vjardin@free.fr>
Cc: <buildroot@buildroot.org>, <tim609@andestech.com>
Subject: Re: [Buildroot] [PATCH 3/4] configs/andes_ae350_45_defconfig: bump to opensbi v1.5
Date: Wed, 5 Nov 2025 20:25:35 +0800	[thread overview]
Message-ID: <aQtCP5SHLUoG9vwu@swlinux02> (raw)
In-Reply-To: <vqod7vwg76gzuo6bzp5jfb5mltauigzwv4aflzt35lakge6g6u@w6lomwzuua43>

Hi Vincent,

On Wed, Oct 29, 2025 at 02:54:57PM +0100, Vincent Jardin wrote:
> [EXTERNAL MAIL]
> 
> Hi Leo,
> 
> On Mon, Oct 27, 2025 at 11:32:41AM +0100, Leo Yu-Chi Liang wrote:
> > This bumps opensbi to v1.5 and add proper hash file.
> >
> > -BR2_TARGET_OPENSBI_CUSTOM_TARBALL_LOCATION="$(call github,riscv,opensbi,22f38ee6c658a660083aa45c4ec6c72f66a17260)/opensbi-22f38ee6c658a660083aa45c4ec6c72f66a17260.tar.gz"
> > -BR2_TARGET_OPENSBI_PLAT="andes/ae350"
> > +BR2_TARGET_OPENSBI_CUSTOM_VERSION=y
> > +BR2_TARGET_OPENSBI_CUSTOM_VERSION_VALUE="1.5"
> 
> Why using opensbi 1.5 knowing that the latest tag is 1.7 ?
>   https://github.com/riscv-software-src/opensbi/tags
> that was released last June.
> 

Thanks for the review.

We are working on a patch to fix current v1.7 OpenSBI for our FPGA board.

For simplicity, we would like to use an older version OpenSBI and update 
the OpenSBI once the patch is merged.
That way we do not need an extra patch/ directory for our OpenSBI.

However, I've just found that v1.6 works.

Do you mind if we bump to v1.6 for this patchset?

Best regards,
Leo

> > +BR2_TARGET_OPENSBI_PLAT="generic"
> 
> Nice that generic can be used.
> 
> Best regards,
>   Vincent
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-11-05 12:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27  3:32 [Buildroot] [PATCH 0/4] Make andes_ae350_45_defconfig more properly maintained Leo Yu-Chi Liang via buildroot
2025-10-27  3:32 ` [Buildroot] [PATCH 1/4] configs/andes_ae350_45_defconfig: Fix post-build.sh Shellcheck error Leo Yu-Chi Liang via buildroot
2025-10-29 13:56   ` Vincent Jardin via buildroot
2025-11-01 17:27   ` Julien Olivain via buildroot
2025-11-04  6:01     ` Leo Liang via buildroot
2025-11-17 19:59   ` Arnout Vandecappelle via buildroot
2025-10-27  3:32 ` [Buildroot] [PATCH 2/4] configs/andes_ae350_45_defconfig: Fix linux tarball source Leo Yu-Chi Liang via buildroot
2025-10-29 20:41   ` Julien Olivain via buildroot
2025-11-04  6:20     ` Leo Liang via buildroot
2025-10-27  3:32 ` [Buildroot] [PATCH 3/4] configs/andes_ae350_45_defconfig: bump to opensbi v1.5 Leo Yu-Chi Liang via buildroot
2025-10-29 13:54   ` Vincent Jardin via buildroot
2025-11-05 12:25     ` Leo Liang via buildroot [this message]
2025-10-27  3:32 ` [Buildroot] [PATCH 4/4] configs/andes_ae350_45_defconfig: bump to uboot v2024.10 Leo Yu-Chi Liang via buildroot
2025-10-29 14:00   ` Vincent Jardin via buildroot
2025-11-05 12:30     ` Leo Liang via buildroot

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=aQtCP5SHLUoG9vwu@swlinux02 \
    --to=buildroot@buildroot.org \
    --cc=tim609@andestech.com \
    --cc=vjardin@free.fr \
    --cc=ycliang@andestech.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