|| ||Linus Torvalds <torvalds-AT-linux-foundation.org> |
|| ||Michael Ellerman <michael-AT-ellerman.id.au> |
|| ||Re: [GIT PULL] ARM MSM updates for 2.6.35-rc1 |
|| ||Wed, 2 Jun 2010 21:26:29 -0700 (PDT)|
|| ||Kevin Hilman <khilman-AT-deeprootsystems.com>,
Daniel Walker <dwalker-AT-codeaurora.org>,
|| ||Article, Thread
On Thu, 3 Jun 2010, Michael Ellerman wrote:
> You can sort of do that today, by just storing a delta, but oldconfig
> will silently turn off things you have enabled if prereqs change, so
> that doesn't really work I think.
I think you can do it today with various hacks. Up to and including
basically doing something that just selects the options you want.
IOW, you could likely have a human-written Kconfig.<platform> file that
define_bool MYPLATFORM y
select .. everything I need ..
or a number of other tricks.
Ingo and the x86 folks (who I really think have done a very good job, and
there really aren't any crazy defconfig files there) have this "make
randconfig" together with scripted requirements so that you can actually
_boot_ the random config, just because the requirements make sure that the
things needed for booting on the test setup are selected.
I forget exactly what the build setup there is (Ingo described it to me
long time ago, but since I don't even want to have a build farm in my
home, I didn't care much).
But we certainly _can_ do a better job than the 'defconfig' thing that was
really never meant for the kind of use it sees in ARM/POWERPC/SH/MIPS, and
that really isn't appropriate for any manual editing (so people just run
"make oldconfig" with tweaking or something, and then use the newly
And I suspect that it really is best to just remove the existing defconfig
files. People can see them in the history to pick up what the heck they
did, but no way will any sane model ever look even _remotely_ like them,
so they really aren't a useful basis for going forward.
But don't worry. It didn't happen this merge window, obviously.
to post comments)