image: Be a little more verbose when checking signatures
authorSimon Glass <sjg@chromium.org>
Wed, 18 Mar 2020 17:43:56 +0000 (11:43 -0600)
committerSimon Glass <sjg@chromium.org>
Wed, 1 Apr 2020 13:45:09 +0000 (07:45 -0600)
It is useful to be a little more specific about what is being checked.
Update a few messages to help with this.

Signed-off-by: Simon Glass <sjg@chromium.org>
common/image-fit.c
tools/image-host.c

index 3d0cd564d833d8563264d355d06f4656989ce4b9..47fc84aa4e3f0224aba7d271beef7266928eb6bb 100644 (file)
@@ -1951,7 +1951,7 @@ int fit_image_load(bootm_headers_t *images, ulong addr,
                fit_uname = fit_get_name(fit, noffset, NULL);
        }
        if (noffset < 0) {
-               puts("Could not find subimage node\n");
+               printf("Could not find subimage node type '%s'\n", prop_name);
                bootstage_error(bootstage_id + BOOTSTAGE_SUB_SUBNODE);
                return -ENOENT;
        }
index 76a361b9d678340fb3ff1166f8619384cf98d478..b3ec197dc9c61e96f5e5a1f2be3456f46b447ed6 100644 (file)
@@ -1034,7 +1034,8 @@ int fit_check_sign(const void *fit, const void *key)
        if (!cfg_noffset)
                return -1;
 
-       printf("Verifying Hash Integrity ... ");
+       printf("Verifying Hash Integrity for node '%s'... ",
+              fdt_get_name(fit, cfg_noffset, NULL));
        ret = fit_config_verify(fit, cfg_noffset);
        if (ret)
                return ret;