CONFIG_DEBUG_MVEBU_UART: Kernel low-level debugging messages via MVEBU UART (old bootloaders)

General informations

The Linux kernel configuration item CONFIG_DEBUG_MVEBU_UART has multiple definitions:

Kernel low-level debugging messages via MVEBU UART (old bootloaders) found in arch/arm/Kconfig.debug

The configuration item CONFIG_DEBUG_MVEBU_UART:

• prompt: Kernel low-level debugging messages via MVEBU UART (old bootloaders)
• type: bool
• depends on: CONFIG_ARCH_MVEBU
• defined in arch/arm/Kconfig.debug
• found in Linux kernels: 3.11–3.19

Help text

Say Y here if you want kernel low-level debugging support on MVEBU based platforms.

This option should be used with the old bootloaders that left the internal registers mapped at 0xd0000000. As of today, this is the case on platforms such as the Globalscale Mirabox or the Plathome OpenBlocks AX3, when using the original bootloader.

If the wrong DEBUG_MVEBU_UART* option is selected, when u-boot hands over to the kernel, the system silently crashes, with no serial output at all.

Kernel low-level debugging messages via MVEBU UART found in arch/arm/Kconfig.debug

The configuration item CONFIG_DEBUG_MVEBU_UART:

• prompt: Kernel low-level debugging messages via MVEBU UART
• type: bool
• depends on: CONFIG_ARCH_MVEBU
• defined in arch/arm/Kconfig.debug
• found in Linux kernels: 3.7–3.10

Help text

Say Y here if you want kernel low-level debugging support on MVEBU based platforms.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: