Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

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

[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

arch/powerpc/Kconfig.debug

+7 −0
Original line number Diff line number Diff line
@@ -151,6 +151,13 @@ config BOOTX_TEXT 


config PPC_EARLY_DEBUG

	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

	prompt "Early debugging console"

arch/powerpc/kernel/udbg.c

+4 −0
Original line number Diff line number Diff line
@@ -57,6 +57,10 @@ void __init udbg_early_init(void) 
#elif defined(CONFIG_PPC_EARLY_DEBUG_CPM)

	udbg_init_cpm();

#endif



#ifdef CONFIG_PPC_EARLY_DEBUG

	console_loglevel = 10;

#endif

}



/* udbg library, used by xmon et al */