The X86_VERBOSE_BOOTUP enables informational output from the decompression
stage with the earlyprintk. If CONFIG_EARLY_PRINTK is not set, there are
no reasons to make CONFIG_X86_VERBOSE_BOOTUP possible for the configuration.

Signed-off-by: Alexander Kuleshov <[email protected]>
---
 arch/x86/Kconfig.debug | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
index 72484a6..53d096b 100644
--- a/arch/x86/Kconfig.debug
+++ b/arch/x86/Kconfig.debug
@@ -22,14 +22,6 @@ config STRICT_DEVMEM
 
          If in doubt, say Y.
 
-config X86_VERBOSE_BOOTUP
-       bool "Enable verbose x86 bootup info messages"
-       default y
-       ---help---
-         Enables the informational output from the decompression stage
-         (e.g. bzImage) of the boot. If you disable this you will still
-         see errors. Disable this if you want silent bootup.
-
 config EARLY_PRINTK
        bool "Early printk" if EXPERT
        default y
@@ -65,6 +57,15 @@ config EARLY_PRINTK_EFI
          This is useful for kernel debugging when your machine crashes very
          early before the console code is initialized.
 
+config X86_VERBOSE_BOOTUP
+       bool "Enable verbose x86 bootup info messages"
+       depends on EARLY_PRINTK
+       default y
+       ---help---
+         Enables the informational output from the decompression stage
+         (e.g. bzImage) of the boot. If you disable this you will still
+         see errors. Disable this if you want silent bootup.
+
 config X86_PTDUMP
        bool "Export kernel pagetable layout to userspace via debugfs"
        depends on DEBUG_KERNEL
-- 
2.4.0.596.ga5fe668

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to