> On Sat, Jul 15, 2006 at 08:45:56AM +0200, Arjan van de Ven wrote: > > On Sat, 2006-07-15 at 08:38 +0200, Sam Ravnborg wrote: > > > On Sat, Jul 15, 2006 at 07:49:08AM +0200, Arjan van de Ven wrote: > > > > On Sat, 2006-07-15 at 01:34 -0400, Dave Jones wrote: > > > > > A lot of prehistoric junk shows up on x86-64 configs. > > > > > > > > > > > > ... but in general it helps compile testing if you're hacking stuff; > > > > if your hacking IDE on x86-64 you now have to compile 32 bit as well to > > > > see if you didn't break the compile for these as well > > > > > > > > So please don't do this, just disable them in your config... > > > > > > An i686 cross compile chain seems to be the natural choice here > > > > the point is that it doesn't fall out naturally, and thus things get > > needlessly missed. > > It seems the main question is: > Is the kernel configuration mainly designed for users or for developers? > > For users, showing drivers for hardware that is not present on their > platform only causes confusion. > > Only developers who want to do compile tests could benefit from > compiling such drivers. > > IMHO the kernel configuration is mainly designed for users. or at least should be. > We could do some kind of (X86_32 || DEVELOPER_COMPILE_TEST). Let's not complicate it more. > Or simply disable this driver on other platforms - these are only > compile errors and amongst all possible problems in the kernel compile > errors are amongst my least worries (obvious error, usually quickly > fixed after the first bug report). --- ~Randy - : send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
