Hi Frank,
On 1/16/26 7:29 PM, Frank Wunderlich wrote:
From: Frank Wunderlich <[email protected]>
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 <[email protected]>
---
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)");
Given that DT node names cannot contain parentheses according to the
Device Tree specification, "(null)" should hopefully not confuse users?
Thus,
Reviewed-by: Quentin Schulz <[email protected]>
Thanks!
Quentin
