lkml.org 
[lkml]   [2010]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ARM defconfig files
On Thu, Jun 03, 2010 at 12:35:42PM -0700, Daniel Walker wrote:
> On Thu, 2010-06-03 at 11:56 -0700, Linus Torvalds wrote:
> >
> > On Thu, 3 Jun 2010, Russell King wrote:
> > >
> > > No amount of reorganising the Kconfig files into a heirarchial manner
> > > (which they already are) helps. Not one bit. Because they already are.
> > > That's not where the problem is.
> >
> > I don't think you read the whole thread.
> >
> > Earlier on, I explained exactly what I wanted: just add some "select"
> > statements to pickt he things you need per the particular target
> > configuration. You seem to have missed that part.
> >
> > In other words, you _can_ encode the information that is in the
> > xyz_defconfig files by doing it in Kconfig.xyz files instead. But you do
> > it in a human-readable manner. And the hierarchical thing is absolutely
> > required for that - otherwise you'd end up with just another form of the
> > current xyz_defconfig.
> >
> > See?
> >
> > In other words, you should be able to basically use "make allnoconfig"
> > together with a Kconfig.xyz file input to select _exactly_ the pieces you
> > need, and nothing else.
>
> If you did this for drivers, what about disabling a driver? If we used
> "select" wouldn't that force all the drivers on without allowing it to
> be unselected?

I already covered that in my (ignored) email where I brought up a
"STD_CONFIG" config symbol, which could be disabled to turn off all
these additional "select"s.

--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:


\
 
 \ /
  Last update: 2010-06-03 21:49    [W:0.096 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site