public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: defconfigs (x86 defconfig: increase CONFIG_LOG_BUF_SHIFT)
Date: Sat, 3 Jan 2009 13:29:50 +0100	[thread overview]
Message-ID: <20090103122949.GA1531@ucw.cz> (raw)
In-Reply-To: <49582A61.6040209@oracle.com>

On Sun 2008-12-28 17:39:45, Randy Dunlap wrote:
> Linux Kernel Mailing List wrote:
> > Author:     Ingo Molnar <mingo@elte.hu>
> > 
> >     x86 defconfig: increase CONFIG_LOG_BUF_SHIFT
> >     
> >     Impact: double the defconfig printk buffer
> >     
> >     Booting defconfigs produces more output than 128K so the output is
> >     truncated - double it to 256K.
> >     
> >     Signed-off-by: Ingo Molnar <mingo@elte.hu>
> > ---
> >  arch/x86/configs/i386_defconfig   |    2 +-
> >  arch/x86/configs/x86_64_defconfig |    2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> 
> Would someone attempt to explain the current purpose of defconfig files,
> please?

For machines like spitz (handheld with 64MB ram, arm, and mostly fixed
configuration) defconfig is very useful. Its basically impossible to
get all the stuff right so that it boots and finds root, otherwise...

For generic PC... well something like distro's config is still nice
starting point, but... 
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2009-01-03 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200812282126.mBSLQ48J004583@hera.kernel.org>
2008-12-29  1:39 ` defconfigs (x86 defconfig: increase CONFIG_LOG_BUF_SHIFT) Randy Dunlap
2009-01-03 12:29   ` Pavel Machek [this message]

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=20090103122949.GA1531@ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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