From: Rick Chen <rick@andestech.com>
To: <sjg@chromium.org>, <ycliang@andestech.com>,
<peterlin@andestech.com>, <rick@andestech.com>,
<rickchen36@gmail.com>
Cc: <u-boot@lists.denx.de>
Subject: [PATCH v2] riscv: binman: Add help message for missing blobs
Date: Fri, 17 Feb 2023 16:57:01 +0800 [thread overview]
Message-ID: <20230217085701.23536-1-rick@andestech.com> (raw)
Add the 'missing-msg' for more detailed output
on missing system firmware.
Signed-off-by: Rick Chen <rick@andestech.com>
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
---
Changes in v2
- Add more descriptions about fw_dynamic.bin
---
arch/riscv/dts/binman.dtsi | 1 +
tools/binman/missing-blob-help | 6 ++++++
2 files changed, 7 insertions(+)
diff --git a/arch/riscv/dts/binman.dtsi b/arch/riscv/dts/binman.dtsi
index b8fc8f7f35..156cb00971 100644
--- a/arch/riscv/dts/binman.dtsi
+++ b/arch/riscv/dts/binman.dtsi
@@ -45,6 +45,7 @@
opensbi_blob: opensbi {
filename = "fw_dynamic.bin";
+ missing-msg = "opensbi";
};
};
diff --git a/tools/binman/missing-blob-help b/tools/binman/missing-blob-help
index c61ca02a35..4448ac9311 100644
--- a/tools/binman/missing-blob-help
+++ b/tools/binman/missing-blob-help
@@ -37,3 +37,9 @@ https://github.com/siemens/k3-rti-wdt.
tee-os:
See the documentation for your board. You may need to build Open Portable
Trusted Execution Environment (OP-TEE) with TEE=/path/to/tee.bin
+
+opensbi:
+See the documentation for your board. The OpenSBI git repo is at
+https://github.com/riscv/opensbi.git
+You may need to build fw_dynamic.bin first and re-build u-boot with
+OPENSBI=/path/to/fw_dynamic.bin
--
2.17.1
next reply other threads:[~2023-02-17 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 8:57 Rick Chen [this message]
2023-02-17 18:20 ` [PATCH v2] riscv: binman: Add help message for missing blobs Yu-Chien Peter Lin
2023-02-17 23:49 ` Simon Glass
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=20230217085701.23536-1-rick@andestech.com \
--to=rick@andestech.com \
--cc=peterlin@andestech.com \
--cc=rickchen36@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--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 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.