DEBUG: inform that output will be both in dmesg and on console from where that measure is enforced in code

This is equivalent of passing debug on kernel command line from coreboot config, even is enabled through config options and saved back in CBFS.

Signed-off-by: Thierry Laurion <insurgo@riseup.net>
This commit is contained in:
Thierry Laurion 2024-12-16 16:27:49 -05:00
parent b5c24f2447
commit 60ba06dab2
No known key found for this signature in database
GPG Key ID: 9A53E1BB3FF00461

View File

@ -101,7 +101,7 @@ if [ "$CONFIG_DEBUG_OUTPUT" = "y" ]; then
#DEBUG and TRACE calls will be in dmesg and on console
# config.user extracted and combined from CBFS had CONFIG_DEBUG_OUTPUT=y
dmesg -n 8
DEBUG "Full debug output enabled from this point. For earlier debug output, enable CONFIG_DEBUG_OUTPUT=y in your board configuration at build time."
DEBUG "Full debug output enabled from this point: output both in dmesg and on console (equivalent of passing debug to kernel cmdline)"
TRACE_FUNC
fi
@ -114,7 +114,6 @@ if [ "$CONFIG_QUIET_MODE" = "y" ]; then
else
echo "Quiet mode enabled at runtime by user configuration: see /tmp/debug.log for additional boot measurements traces past this point" >/dev/tty0
echo "To suppress earlier boot measurements traces, enable CONFIG_QUIET_MODE=y in your board configuration at build time." >/dev/tty0
" >/dev/tty0
fi
fi