Re: ARM defconfig files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux