Commit 7ee17466 authored by Benjamin Herrenschmidt's avatar Benjamin Herrenschmidt Committed by Paul Mackerras

[POWERPC] Early debug forces console log level to max

This makes the early debug option force the console loglevel
to the max.  The early debug option is meant to catch messages very
early in the kernel boot process, in many cases, before the kernel
has a chance to parse the "debug" command line argument.  Thus it
makes sense when CONFIG_PPC_EARLY_DEBUG is set, to force the console
log level to the max at boot time.
Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
parent 837c54db
...@@ -151,6 +151,13 @@ config BOOTX_TEXT ...@@ -151,6 +151,13 @@ config BOOTX_TEXT
config PPC_EARLY_DEBUG config PPC_EARLY_DEBUG
bool "Early debugging (dangerous)" bool "Early debugging (dangerous)"
help
Say Y to enable some early debugging facilities that may be available
for your processor/board combination. Those facilities are hacks
intended to debug problems early during boot, this should not be
enabled in a production kernel.
Note that enabling this will also cause the kernel default log level
to be pushed to max automatically very early during boot
choice choice
prompt "Early debugging console" prompt "Early debugging console"
......
...@@ -57,6 +57,10 @@ void __init udbg_early_init(void) ...@@ -57,6 +57,10 @@ void __init udbg_early_init(void)
#elif defined(CONFIG_PPC_EARLY_DEBUG_CPM) #elif defined(CONFIG_PPC_EARLY_DEBUG_CPM)
udbg_init_cpm(); udbg_init_cpm();
#endif #endif
#ifdef CONFIG_PPC_EARLY_DEBUG
console_loglevel = 10;
#endif
} }
/* udbg library, used by xmon et al */ /* udbg library, used by xmon et al */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment