From: E Shattow <e@freeshell.de>
To: Zhouqi Jiang <luojia@rustsbi.com>, u-boot@lists.u-boot-project.org
Cc: trini@konsulko.com, tim609@andestech.com, leo.liang@sifive.com,
me@ziyao.cc, sjg@chromium.org, alpernebiyasak@gmail.com,
jiangzhouqi2025@iscas.ac.cn, plucky@rustsbi.com,
Chao Liu <chao.liu@processmission.com>,
Daniel Maslowski <info@orangecms.org>
Subject: Re: [PATCH v2 0/3] riscv: Support RustSBI through the FW_DYNAMIC handoff
Date: Thu, 19 Nov 2026 02:31:52 -0800 [thread overview]
Message-ID: <319d91fc-79ba-491f-b5e6-234520c7ae60@freeshell.de> (raw)
In-Reply-To: <B92B10779C0D9EDB+20261119091842.3062208-1-luojia@rustsbi.com>
Hi Zhougi,
On 11/19/26 01:18, Zhouqi Jiang wrote:
> RustSBI Prototyper dynamic firmware accepts the FW_DYNAMIC handoff
> already used by U-Boot SPL. This series documents that compatibility
> and lets users provide the firmware with RUSTSBI= through the
> existing opensbi binman entry.
>
> The first patch makes the SBI_V02 help text firmware-independent.
> The second adds the build input alias, a binman test and help for a
> missing firmware blob. The third describes supported firmware and
> the effects of the scratch options in the architecture guide and
> SPL Kconfig help.
>
> I'd appreciate Tom's and Yao's feedback on two points from the v1
> discussion.
>
> 1. Patch 2 keeps RUSTSBI= as an alias for OPENSBI=. Both use the same
> FIT entry and SPL handoff. Would you prefer to keep the alias or
> use OPENSBI= for both firmware implementations?
Correct, keep OPENSBI= and no additional aliases please.
Arguably this should be a few bytes shorter as 'SBI=' however the effort
to change this and all the documentation and all references to U-Boot
from external write-ups and documentation is without any particular
purpose. "OpenSBI" was the first mover, and as that goes in technology
the first mover tends to be the "Google it" or "Open up your Excel"...
OPENSBI= has the meaning here of "an SBI implementation" and we must use
that for consistency. Adding an alias adds to technical debt without any
particular purpose.
>
> 2. The FIT description and SPL debug message currently say OpenSBI
> for both firmware binaries. The U-Boot "sbi" command identifies
> the implementation at runtime. Would it be useful to pass the
> firmware name through for display, or should we keep the current
> labels?
If you have "sbi" command enabled then you probably already know the SBI
implementation linked or packaged with a build of U-Boot, and if you do
not then (depending on scratch options at OpenSBI build time e.g.) a
huge banner gets printed with this information before U-Boot main app
invocation. Is there a common use for this that "sbi" command should be
enabled for most users?
>
> Changes in v2:
> - Split the series into three focused patches.
> - Reuse the existing SPL handoff and opensbi FIT entry.
> - Put the firmware documentation in the RISC-V architecture guide.
>
> v1: https://lore.kernel.org/u-boot/2744044E69DD25E5%2B20261115143808.1812787-1-luojia@rustsbi.com/
>
> Zhouqi Jiang (3):
> riscv: Describe SBI_V02 in terms of the SBI version
> binman: Accept RUSTSBI as an alias for OPENSBI
> riscv: Document SBI firmware support in SPL
>
> Makefile | 6 ++++--
> arch/riscv/Kconfig | 3 +--
> common/spl/Kconfig | 8 +++++++-
> doc/arch/riscv.rst | 17 +++++++++++++++++
> tools/binman/ftest.py | 9 +++++++++
> tools/binman/missing-blob-help | 2 ++
> 6 files changed, 40 insertions(+), 5 deletions(-)
>
> base-commit: f6e8f09ed39347359ebddd983b96993c78b4ec7d
-E
next prev parent reply other threads:[~2026-11-19 10:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 14:38 [PATCH] riscv: Add RustSBI firmware support Zhouqi Jiang
2026-11-15 17:10 ` Tom Rini
2026-11-16 5:42 ` Zhouqi Jiang
2026-11-16 13:02 ` Yao Zi
2026-11-16 15:15 ` Zhouqi Jiang
2026-11-19 11:41 ` Yao Zi
2026-11-19 12:00 ` Zhouqi Jiang
2026-11-16 12:45 ` Yao Zi
2026-11-19 9:18 ` [PATCH v2 0/3] riscv: Support RustSBI through the FW_DYNAMIC handoff Zhouqi Jiang
2026-11-19 10:31 ` E Shattow [this message]
[not found] ` <20261119091842.3062208-1-luojia@rustsbi.com>
2026-11-19 9:18 ` [PATCH v2 1/3] riscv: Describe SBI_V02 in terms of the SBI version Zhouqi Jiang
2026-11-19 10:43 ` E Shattow
2026-11-19 12:08 ` Yao Zi
2026-11-19 9:18 ` [PATCH v2 2/3] binman: Accept RUSTSBI as an alias for OPENSBI Zhouqi Jiang
2026-11-19 10:47 ` E Shattow
2026-11-19 9:18 ` [PATCH v2 3/3] riscv: Document SBI firmware support in SPL Zhouqi Jiang
2026-11-19 11:14 ` E Shattow
2026-11-19 12:05 ` Zhouqi Jiang
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=319d91fc-79ba-491f-b5e6-234520c7ae60@freeshell.de \
--to=e@freeshell.de \
--cc=alpernebiyasak@gmail.com \
--cc=chao.liu@processmission.com \
--cc=info@orangecms.org \
--cc=jiangzhouqi2025@iscas.ac.cn \
--cc=leo.liang@sifive.com \
--cc=luojia@rustsbi.com \
--cc=me@ziyao.cc \
--cc=plucky@rustsbi.com \
--cc=sjg@chromium.org \
--cc=tim609@andestech.com \
--cc=trini@konsulko.com \
--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 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.