path: root/arch/powerpc/Kconfig.debug
diff options
authorBenjamin Herrenschmidt <benh@kernel.crashing.org>2007-12-11 14:48:24 +1100
committerPaul Mackerras <paulus@samba.org>2007-12-11 15:43:35 +1100
commit7ee17466b6ac3b63ce87492d080e15e7f144f7d2 (patch)
treec444e78f104dd0df087f71612b63f1189150f4a4 /arch/powerpc/Kconfig.debug
parent837c54db21fc7047af75f3fe4295e32106449e34 (diff)
[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: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'arch/powerpc/Kconfig.debug')
1 files changed, 7 insertions, 0 deletions
diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug
index 6a79fe43e22..d20ccf5f2ca 100644
--- a/arch/powerpc/Kconfig.debug
+++ b/arch/powerpc/Kconfig.debug
@@ -151,6 +151,13 @@ config BOOTX_TEXT
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
prompt "Early debugging console"