From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about kernel defconfig
Date: Mon, 22 Nov 2010 18:33:27 +0100 [thread overview]
Message-ID: <20101122183327.1285c439@surf> (raw)
Hello Sam,
I am currently working on cleaning up how Buildroot handles board
configuration [1]. As part of this clean up, I'd like to move away from
full kernel .config files and instead use minimal kernel configs (only
non-default options are stored, the kernel configuration files are
produced with savedefconfig).
So, for example for the Qemu Versatile platform, I have the kernel
configuration file visible at
http://git.buildroot.net/~tpetazzoni/git/buildroot/tree/board/qemu/arm-versatile/linux-2.6.36.config?h=for-2010.11/boards-cleanup&id=8033fd6cbacfa96a3bcfce74caad8c423bf60cd1.
When Buildroot configures the kernel, it simply copies the given kernel
configuration file to .config into the kernel source tree. See
http://git.buildroot.net/buildroot/tree/linux/linux.mk#n89.
Unfortunately, with those minimal configuration files, the kernel
"Restart config" and then asks interactively for the value of all
options not specificied in the minimal configuration file.
I'd like to have the same behaviour the kernel has when using its own
internal defconfigs files from arch/$(ARCH)/configs. Is this possible ?
Did I miss something totally obvious ?
Thanks,
Thomas
[1]
http://git.buildroot.net/~tpetazzoni/git/buildroot/log/?h=for-2010.11/boards-cleanup
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2010-11-22 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 17:33 Thomas Petazzoni [this message]
2010-11-22 21:33 ` [Buildroot] Question about kernel defconfig Sam Ravnborg
2010-11-23 21:31 ` Thomas Petazzoni
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=20101122183327.1285c439@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox