public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_EARLY_PRINTK
Date: Sat, 16 Mar 2013 16:08:38 +0100	[thread overview]
Message-ID: <1363446518.12329.5.camel@localhost.localdomain> (raw)
In-Reply-To: <5140D9DF.4010506@infradead.org>

Am Mittwoch, den 13.03.2013, 12:56 -0700 schrieb Randy Dunlap:
> On 03/13/13 10:15, Thomas Meyer wrote:
> > Hi,
> > 
> >  -*- Early printk 
> > 
> > help text says:
> > "You should normally N here, unless you want to debug such a crash.
> > (Depends on: EXPERT [=n])"
> > 
> > How to normally N here?
> 
> You'll have to enable CONFIG_EXPERT and then you can disable EARLY_PRINTK.
> 
> You may even have to disable CONFIG_EMBEDDED before you can enable
> CONFIG_EXPERT (I did).
> 
> Too many hoops to have to jump through.   :(
> 

Yes,

so why not do this? As the text to EARLY_PRINTK explains?

diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
index b322f12..d6c2d89 100644
--- a/arch/x86/Kconfig.debug
+++ b/arch/x86/Kconfig.debug
@@ -32,7 +32,7 @@ config X86_VERBOSE_BOOTUP
 
 config EARLY_PRINTK
        bool "Early printk" if EXPERT
-       default y
+       default n
        ---help---
          Write kernel log output directly into the VGA buffer or to a
serial
          port.




  reply	other threads:[~2013-03-16 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 17:15 CONFIG_EARLY_PRINTK Thomas Meyer
2013-03-13 19:56 ` CONFIG_EARLY_PRINTK Randy Dunlap
2013-03-16 15:08   ` Thomas Meyer [this message]
2013-03-16 17:38     ` CONFIG_EARLY_PRINTK Randy Dunlap
2013-03-16 20:10       ` CONFIG_EARLY_PRINTK Geert Uytterhoeven
2013-03-22 14:07       ` CONFIG_EARLY_PRINTK Thomas Meyer
2013-03-25 23:23         ` CONFIG_EARLY_PRINTK Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1363446518.12329.5.camel@localhost.localdomain \
    --to=thomas@m3y3r.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox