Skip to contentSkip to conversation

tighten ATA kconfig dependancies

DISCUSSION Randy Dunlap 1 participant 1 message Jul 16, 2006 libata

lore
Share & tools
lore
#0 lore raw
Quoted 11 lines · Arjan van de Ven
Quoted 8 lines · Sam Ravnborg
Quoted 7 lines · Arjan van de Ven
Quoted 6 lines · Dave Jones
Quoted 1 line

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

Quoted 12 lines
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

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?

Quoted 7 lines

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.

Quoted 1 line

We could do some kind of (X86_32 || DEVELOPER_COMPILE_TEST).

Let's not complicate it more.

Quoted 4 lines

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