From: Yao Zi <me@ziyao.cc>
To: Zhouqi Jiang <luojia@rustsbi.com>, trini@konsulko.com
Cc: u-boot@lists.u-boot-project.org, tim609@andestech.com,
leo.liang@sifive.com, me@ziyao.cc, sjg@chromium.org,
alpernebiyasak@gmail.com, jiangzhouqi2025@iscas.ac.cn,
plucky@rustsbi.com
Subject: Re: [PATCH] riscv: Add RustSBI firmware support
Date: Mon, 16 Nov 2026 13:02:55 +0000 [thread overview]
Message-ID: <avr-_7CNcFit18nw@pie> (raw)
In-Reply-To: <0E589B613DC4FA4B+20261116054232.1930964-2-luojia@rustsbi.com>
Hi Zhouqi,
Please quote the context on reply, so the mail is easier to read. I'm
adding Tom's comment back here.
> > To be clear, I think all of the changes to make things more clearly
> > generic here are good. At first read, it looks like aside from display
> > strings and a different scratch options value, RustSBI and OpenSBI are
> > interchangeable as far as U-Boot is concerned? If so, I'd like to
> > explore continuing down that path more.
On Mon, Nov 16, 2026 at 01:42:33PM +0800, Zhouqi Jiang wrote:
> Hi Tom,
>
> Thanks. You are right: RustSBI and OpenSBI are interchangeable here because
> RustSBI implements OpenSBI's FW_DYNAMIC handoff protocol. This reflects
> ecosystem compatibility rather than a formal RISC-V standard for
> inter-firmware handoff.
So if RustSBI could be supported through OpenSBI's handoff protocol, why
not simply keep the current OpenSBI stuff as-is, only replace the
fw_dynamic.bin with RustSBI's binary?
From the view of this patch, I don't see any improvements by separating
RustSBI stuff out for the current situation.
> I initially considered merging the tags, but I now prefer to keep
> SPL_OPENSBI and SPL_RUSTSBI separate while moving the shared handoff code into
> a common path. This keeps firmware-specific details, such as scratch options,
> explicit and leaves room for other SBI implementations.
However, scratch options could be modified through Kconfig options
easily. Even with a separate Kconfig option introduced, others still
need to alternate it to use RustSBI-compatible scratch options.
So I think, like what I have said before, a documentation to explain
support status of different SBI implementations, and
SPL_OPENSBI_SCRATCH_OPTIONS' effects on them, might be more appropriate.
A documentation would also help users of boards whose maintainers
haven't/won't update their defconfig/documentation for RustSBI.
> If this matches your understanding, I'll prepare a v2 along these lines.
Thus I'm against the idea of adding a separate Kconfig option for
RustSBI, at least for now where it brings no real benefits.
> Best,
> Zhouqi
--
Thanks,
Yao Zi
Meow-mrrp-mrow, I'm a cat.
next prev parent reply other threads:[~2026-11-16 13:03 UTC|newest]
Thread overview: 6+ 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 [this message]
2026-11-16 15:15 ` Zhouqi Jiang
2026-11-16 12:45 ` Yao Zi
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=avr-_7CNcFit18nw@pie \
--to=me@ziyao.cc \
--cc=alpernebiyasak@gmail.com \
--cc=jiangzhouqi2025@iscas.ac.cn \
--cc=leo.liang@sifive.com \
--cc=luojia@rustsbi.com \
--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.