From: Frank Wunderlich <linux@fw-web.de>
To: Tom Rini <trini@konsulko.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Simon Glass <sjg@chromium.org>
Cc: Frank Wunderlich <frank-w@public-files.de>, u-boot@lists.denx.de
Subject: [PATCH v2] boot/fit: print name of config node not found
Date: Fri, 16 Jan 2026 19:29:02 +0100 [thread overview]
Message-ID: <20260116182903.20652-1-linux@fw-web.de> (raw)
From: Frank Wunderlich <frank-w@public-files.de>
Show name of configuration node which was not found.
current state gives no hint if fit image is wrong or the requested name.
Could not find configuration node
load of <NULL> failed
After this patch we see name like this:
Could not find configuration node '#ov-test'
load of <NULL> failed
Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
---
v2
- handle null
---
boot/image-fit.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/boot/image-fit.c b/boot/image-fit.c
index 2d040e38d97b..85026c2d1d02 100644
--- a/boot/image-fit.c
+++ b/boot/image-fit.c
@@ -2125,7 +2125,8 @@ int fit_image_load(struct bootm_headers *images, ulong addr,
if (ret < 0 && ret != -EINVAL)
ret = fit_conf_get_node(fit, fit_uname_config);
if (ret < 0) {
- puts("Could not find configuration node\n");
+ printf("Could not find configuration node '%s'\n",
+ fit_uname_config ? fit_uname_config : "(null)");
bootstage_error(bootstage_id +
BOOTSTAGE_SUB_NO_UNIT_NAME);
return -ENOENT;
--
2.43.0
next reply other threads:[~2026-01-16 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 18:29 Frank Wunderlich [this message]
2026-01-19 9:40 ` [PATCH v2] boot/fit: print name of config node not found Quentin Schulz
2026-01-28 14:02 ` Tom Rini
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=20260116182903.20652-1-linux@fw-web.de \
--to=linux@fw-web.de \
--cc=frank-w@public-files.de \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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