Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - E index
The Linux kernel configuration item CONFIG_EARLY_PRINTK has multiple definitions:
arch/nios2/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_TTYEnable early printk on console. This is useful for kernel debugging when your machine crashes very early before the console code is initialized. You should normally say N here, unless you want to debug such a crash.
arch/x86/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_EXPERTWrite kernel log output directly into the VGA buffer or to a serial port.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally say N here, unless you want to debug such a crash.
arch/um/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
(none)Write kernel log output directly to stdout.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized.
arch/sh/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_SH_STANDARD_BIOSSay Y here to redirect kernel printk messages to the serial port used by the SH-IPL bootloader, starting very early in the boot process and ending when the kernel's serial console is initialised. This option is only useful while porting the kernel to a new machine, when the kernel may crash or hang before the serial console is initialised. If unsure, say N.
arch/mips/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
( CONFIG_EXPERT ) && ( CONFIG_SYS_HAS_EARLY_PRINTK )This option enables special console drivers which allow the kernel to print messages very early in the bootup process.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation, it is not recommended because it looks ugly on some machines and doesn't cooperate with an X server. You should normally say N here, unless you want to debug such a crash.
arch/m68k/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_MMU_MOTOROLAWrite kernel log output directly to a serial port. Where implemented, output goes to the framebuffer as well. PROM console functionality on Sun 3x is not affected by this option.
Pass "earlyprintk" on the kernel command line to get a boot console.
This is useful for kernel debugging when your machine crashes very early, i.e. before the normal console driver is loaded. You should normally say N here, unless you want to debug such a crash.
arch/arm/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_DEBUG_LLSay Y here if you want to have an early console using the kernel low-level debugging functions. Add earlyprintk to your kernel parameters to enable this console.
arch/s390/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/powerpc/KconfigThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/hexagon/KconfigThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/alpha/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_ALPHA_GENERIC || CONFIG_ALPHA_SRM(none)
arch/unicore32/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
(none)Write kernel log output directly into the ocd or to a serial port.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally N here, unless you want to debug such a crash.
arch/riscv/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/riscv/KconfigThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/microblaze/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_SERIAL_UARTLITE_CONSOLE || CONFIG_SERIAL_8250_CONSOLEThis option turns on/off early printk messages to console. First Uartlite node is taken.
arch/tile/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_EXPERT && CONFIG_DEBUG_KERNELWrite kernel log output directly via the hypervisor console.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd. You should normally N here, unless you want to debug such a crash.
arch/blackfin/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
(none)This option enables special console drivers which allow the kernel to print messages very early in the bootup process.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. After enabling this feature, you must add "earlyprintk=serial,uart0,57600" to the command line (bootargs). It is safe to say Y here in all cases, as all of this lives in the init section and is thrown away after the kernel boots completely.
arch/arc/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_EMBEDDEDWrite kernel log output directly into the VGA buffer or to a serial port.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally N here, unless you want to debug such a crash.
arch/arm64/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
(none)Say Y here if you want to have an early console using the earlyprintk=<name>[,<addr>][,<options>] kernel parameter. It is assumed that the early console device has been initialised by the boot loader prior to starting the Linux kernel.
arch/sh/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_SH_STANDARD_BIOS || CONFIG_EARLY_SCIF_CONSOLESay Y here to redirect kernel printk messages to the serial port used by the SH-IPL bootloader, starting very early in the boot process and ending when the kernel's serial console is initialised. This option is only useful porting the kernel to a new machine, when the kernel may crash or hang before the serial console is initialised. If unsure, say N.
On devices that are running SH-IPL and want to keep the port initialization consistent while not using the BIOS callbacks, select both the EARLY_SCIF_CONSOLE and SH_STANDARD_BIOS, using the kernel command line option to toggle back and forth.
arch/mips/KconfigThe configuration item CONFIG_EARLY_PRINTK:
( CONFIG_EMBEDDED && CONFIG_DEBUG_KERNEL ) && ( CONFIG_SYS_HAS_EARLY_PRINTK )This option enables special console drivers which allow the kernel to print messages very early in the bootup process.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation, it is not recommended because it looks ugly on some machines and doesn't cooperate with an X server. You should normally say N here, unless you want to debug such a crash.
arch/sh64/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/i386/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_EMBEDDED && CONFIG_DEBUG_KERNELWrite kernel log output directly into the VGA buffer or to a serial port.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally N here, unless you want to debug such a crash.
arch/x86_64/KconfigThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/mips/cobalt/KconfigThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_MIPS_COBALTProvide early console support by direct access to the on board UART. The UART must have been previously initialised by the boot loader.
arch/mips/KconfigThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/frv/Kconfig.debugThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_EMBEDDED && CONFIG_DEBUG_KERNELWrite kernel log output directly into the VGA buffer or to a serial port.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally N here, unless you want to debug such a crash.
arch/ppc64/KconfigThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/frv/KconfigThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_EMBEDDED && CONFIG_DEBUG_KERNELWrite kernel log output directly into the VGA buffer or to a serial port.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally N here, unless you want to debug such a crash.
arch/sh64/KconfigThe configuration item CONFIG_EARLY_PRINTK:
(none)(none)
arch/sh/KconfigThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_SH_STANDARD_BIOS || CONFIG_EARLY_SCIF_CONSOLESay Y here to redirect kernel printk messages to the serial port used by the SH-IPL bootloader, starting very early in the boot process and ending when the kernel's serial console is initialised. This option is only useful porting the kernel to a new machine, when the kernel may crash or hang before the serial console is initialised. If unsure, say N.
arch/i386/KconfigThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_EMBEDDEDWrite kernel log output directly into the VGA buffer or to a serial port.
This is useful for kernel debugging when your machine crashes very early before the console code is initialized. For normal operation it is not recommended because it looks ugly and doesn't cooperate with klogd/syslogd or the X server. You should normally N here, unless you want to debug such a crash.
arch/alpha/KconfigThe configuration item CONFIG_EARLY_PRINTK:
CONFIG_ALPHA_GENERIC || CONFIG_ALPHA_SRM(none)
Raw data from LKDDb:
(none)This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).
The data is retrived from:
Popular queries:
Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - E index
Automatically generated (in year 2025). See also LKDDb sources on GitLab