U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <me@ziyao.cc>
To: Martin Husemann <martin@NetBSD.org>, u-boot@lists.u-boot-project.org
Cc: Yao Zi <me@ziyao.cc>
Subject: Re: RiscV SBI incompatibilities?
Date: Thu, 12 Nov 2026 10:59:50 +0000	[thread overview]
Message-ID: <avWcJkgU6xFCZS0Q@pie> (raw)
In-Reply-To: <avSOoJFxsR6hDuUd@pie>

On Wed, Nov 11, 2026 at 03:49:52PM +0000, Yao Zi wrote:
> On Wed, Nov 11, 2026 at 03:35:48PM +0100, Martin Husemann wrote:
> > Hi folks,
> > 
> > maybe I tried something stupid, but it felt like a good idea at first.
> > 
> > I am updating my VisionFive 2 board from an oldish installation with
> > U-Boot 2024.10.
> > 
> > To have as few moving parts as possible, I build 2026.10 with the same SBI
> > that I had lying around from the original 2024.10 build, which happend
> > to be OpenSBI 1.4.
> > 
> > This failed spectacularily: most sbc_* calls for HSM fail with 
> > -3 (SBI_ERR_INVALID_PARAM).
> > 
> > A few calls worked, like sbi_hart_start() and sbi_hart_get_status(),
> > which told me the hartids I was using were valid, but then doing
> > e.g. sbi_send_ipi() or sbi_remote_sfence_vma() failed.
> > 
> > Does this ring a bell? Is it expected? Did I overlook a "minimal SBI version
> > 1.X" somewhere?
> 
> doc/board/starfive/jh7110_common.rst says,
> 
> > 3.  U-Boot for JH-7110 requires OpenSBI v1.5+ generic platform object
> >     fw_dynamic.bin to be included in the Flattened Image Tree blob. OpenSBI may
> >     first be built as below:
> 
> I had a brief look through the changes from v1.4 to v1.5, and suspect it
> has something to do with OpenSBI commit c5be0e1ed1fa ("lib: utils/ipi:
> Skip initialize ipi when dt is not enabled")[1], but don't confirm it :)

Totally unnecessary, just out of curiosity, could you please send a list
of failed sbi calls and their corresponding error codes? From this I
could probably find out whether it's related to the OpenSBI commit :)

Feel free to ignore this message if you don't want to :)

> > Martin
> 
> -- 
> Thanks,
> Yao Zi
> 
> Meow-mrrp-mrow, I'm a cat.
> 
> [1]: https://github.com/riscv-software-src/opensbi/commit/c5be0e1ed1fa17b9f9abb49e80db014e067523e4

-- 
Thanks,
Yao Zi

Meow-mrrp-mrow, I'm a cat.

  parent reply	other threads:[~2026-11-12 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 14:35 RiscV SBI incompatibilities? Martin Husemann
2026-11-11 15:49 ` Yao Zi
2026-11-12 10:08   ` Martin Husemann
2026-11-12 10:59   ` Yao Zi [this message]
2026-11-12 11:09     ` Martin Husemann

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=avWcJkgU6xFCZS0Q@pie \
    --to=me@ziyao.cc \
    --cc=martin@NetBSD.org \
    --cc=u-boot@lists.u-boot-project.org \
    /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