From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about kernel defconfig
Date: Tue, 23 Nov 2010 22:31:58 +0100 [thread overview]
Message-ID: <20101123223158.1a555b29@surf> (raw)
In-Reply-To: <20101122213317.GA10532@merkur.ravnborg.org>
Hello,
On Mon, 22 Nov 2010 22:33:18 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:
> kconfig behaves in different ways depending on what type of input it receives.
> To use the minimal configs generated by "savedefconfig" you need to read
> them using "--defconfig".
> And there is today no way to specify your own defconfig file.
>
> One workaround could be to copy the file to:
>
> arch/$ARCH/configs/buildroot_defconfig
>
> And then use:
>
> make buildroot_defconfig
>
> This will read the minimal config in the same way the kernel usually does it.
Ok, thanks. I thought about this in the past, but found it a bit hacky.
But as there's no other simple solution, I just implemented that.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-11-23 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 17:33 [Buildroot] Question about kernel defconfig Thomas Petazzoni
2010-11-22 21:33 ` Sam Ravnborg
2010-11-23 21:31 ` Thomas Petazzoni [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=20101123223158.1a555b29@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.