On Wed, Dec 17, 2014 at 12:58 PM, Joe Perches <joe@xxxxxxxxxxx> wrote:
> It seems like early_printk can be configured into
> a few architectures but also appear not to be used.
>
> $ git grep -w "early_printk"
[snip]
> arch/mips/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
Nowadays I try to use OF_EARLYCON whenever possible, but when that has
been unavailable, I have used arch/mips/kernel/early_printk.c to get
console output before the serial driver is initialized. It runs very
early in the boot sequence and has very few dependencies, which makes
it useful for board bringup.
At least on MIPS, the EARLY_PRINTK implementation registers itself as
a console and works with standard printk() calls. It doesn't rely on
arch/driver code explicitly calling early_printk().
Side note: looking through kernel/printk/printk.c it looks like
there's a space missing in the description string:
MODULE_PARM_DESC(ignore_loglevel, "ignore loglevel setting, to"
"print all kernel messages to the console.");
But since CONFIG_PRINTK is a bool option, I don't know if the
description string actually shows up anywhere. Should it be converted
into a comment?
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
