Re: [PATCH] kconfig: untangle EXPERT and EMBEDDED

[Russell King - ARM Linux <linux@arm.linux.org.uk>]

On Wed, Jan 18, 2012 at 12:28:30PM -0800, Andrew Morton wrote:
> I can see an argument for retaining EXPERIMENTAL: as a way of telling
> people that the particular feature might not yet be ready for prime
> time.  But I suggest that we tip both CONFIG_EXPERT and CONFIG_EMBEDDED
> into the ole bit bucket.  What do you guys think would be the negative
> consequences of doing this?

The negative effect is that x86 will continue wanting to have things
like ATKBD enabled, where that's not appropraite for other architectures.
Eg, on ARM, we really want that to default to 'n' for the fast majority
of our platforms.

I've lost count of the times in the past that I ended up with ATKBD
inappropriately enabled in the past, or I8042 or something like that,
and had problems as a result.

I'll also mention that I've given up with the Kconfig tools - my way of
configuring the kernel now is solidly an editor on .config and make
oldconfig, even for simple changes like changing the compression format
for zImage.

The last time I seriously interacted with the Kconfig tools was when I
built 3.1.8 for the laptop, from a 2.6.35.14 based config - and spent
something like 30 minutes dealing with 'make oldconfig', each option
occupying about a second of my attention before giving it an answer.

I believe kernel configuration has positively become a nightmare, one
which no one sane would undertake.