From: Martin Husemann <martin@NetBSD.org>
To: u-boot@lists.u-boot-project.org
Subject: RiscV SBI incompatibilities?
Date: Wed, 11 Nov 2026 15:35:48 +0100 [thread overview]
Message-ID: <avR9RCMQHL8TZIAR@big-apple.aprisoft.de> (raw)
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?
Martin
next reply other threads:[~2026-11-11 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 14:35 Martin Husemann [this message]
2026-11-11 15:49 ` RiscV SBI incompatibilities? Yao Zi
2026-11-12 10:08 ` Martin Husemann
2026-11-12 10:59 ` Yao Zi
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=avR9RCMQHL8TZIAR@big-apple.aprisoft.de \
--to=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