From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Subject: What about make mergeconfig ?
Date: Wed, 25 Oct 2006 15:46:04 +1000 [thread overview]
Message-ID: <1161755164.22582.60.camel@localhost.localdomain> (raw)
Hi folks !
I'm not good enough at make and friends to do that myself without
spending a lot more time than I have at hand, but I figured it might be
something doable in a blink for whoever knows Kconfig guts :)
What about something like:
make mergeconfig <path_to_file>
That would merge all entries in the specified file with the
current .config. By mergeing, that basically means that rule:
N + N = N
m + N = m
Y + N = Y
m + Y = Y
(that is, we basically take for each entry max(.config, merge file)
The idea here is that on archs like powerpc, we have the ability to
build kernels that can boot several platforms. However, the defconfigs
we ship (g5_defconfig, pseries_defconfig, maple_defconfig, cell... ) are
tailored for one platform.
Now, if (for testing typically) I want to build a kernel that boots (and
has all the necessary drivers) for both a g5 and a cell, I need to start
from one of the defconfigs (the g5 one) and basically add in manually
all the bits necessary from the other one (the cell one).
Thus it might be useful to have a mecanism to automate that...
Thanks in advance for whichever guru wants to have a look at this :)
Cheers,
Ben.
next reply other threads:[~2006-10-25 5:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 5:46 Benjamin Herrenschmidt [this message]
2006-10-25 6:59 ` What about make mergeconfig ? David Woodhouse
2006-10-25 10:01 ` Jesper Juhl
2006-10-25 13:52 ` Benjamin Herrenschmidt
2006-10-25 10:18 ` Dick Streefland
2006-10-25 11:39 ` Jan Engelhardt
2006-10-25 12:07 ` Dick Streefland
2006-10-26 8:00 ` Jan Engelhardt
2006-10-26 9:03 ` Geert Uytterhoeven
2006-10-26 11:25 ` Jan Engelhardt
2006-10-26 12:00 ` Geert Uytterhoeven
2006-10-27 9:58 ` Jan Engelhardt
2006-10-27 11:14 ` Geert Uytterhoeven
2006-10-25 17:41 ` Christoph Lameter
2006-10-26 10:50 ` Samuel Tardieu
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=1161755164.22582.60.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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