On 16.08.25 01:31, Simon Glass wrote:
From: Simon Glass <sjg@chromium.org>
Provides some debugging info while doing bootm processing.
Signed-off-by: Simon Glass <sjg@chromium.org> ---
arch/arm/lib/bootm.c | 6 ++++++ 1 file changed, 6 insertions(+)
diff --git a/arch/arm/lib/bootm.c b/arch/arm/lib/bootm.c index cb365d95c7b..9d8c9a813dc 100644 --- a/arch/arm/lib/bootm.c +++ b/arch/arm/lib/bootm.c @@ -11,6 +11,8 @@ * Copyright (C) 2001 Erik Mouw (J.A.K.Mouw@its.tudelft.nl) */
+#define LOG_CATEGORY LOGC_BOOT + #include <bootm.h> #include <bootstage.h> #include <command.h> @@ -349,20 +351,24 @@ int do_bootm_linux(int flag, struct bootm_info *bmi) { struct bootm_headers *images = bmi->images;
+ log_debug("boot linux flag %x\n", flag); /* No need for those on ARM */ if (flag & BOOTM_STATE_OS_BD_T || flag & BOOTM_STATE_OS_CMDLINE) return -1;
if (flag & BOOTM_STATE_OS_PREP) { + log_debug("linux prep\n");
log_debug("Preparing to boot Linux\n");
boot_prep_linux(images); return 0; }
if (flag & (BOOTM_STATE_OS_GO | BOOTM_STATE_OS_FAKE_GO)) { + log_debug("go/fake\n");
I would suggest to use debug messages that users are able to understand. I wouldn't have a clue what "go/fake" might mean.
boot_jump_linux(images, flag); return 0; }
+ log_debug("cont\n");
This message isn't human intelligible either. Is the binary "contaminated"? How about log_debug("Preparing to boot Linux\n"); like above. Best regards Heinrich
boot_prep_linux(images); boot_jump_linux(images, flag); return 0;