>> I think we should not silently assume we should use the PCI BIOS
>> if the user has selected neither PCI BIOS nor PCI direct access.
>> If neither is selected, the PCI driver just refuses to compile and
>> tells the user he should configure it properly.
> That appears to confuse the user base greatly. Maybe someone should
> implement either/or in Config.in ?
Does the following patch help here? If so, propogate it as required
across architectures...
Best wishes from Riley.
===8<=== CUT ===>8===
--- linux-2.1.131/arch/i386/config.in.orig Sun Dec 20 15:42:42 1998
+++ linux-2.1.131/arch/i386/config.in Wed Dec 23 08:45:01 1998
@@ -36,15 +36,13 @@
comment 'General setup'
bool 'Networking support' CONFIG_NET
bool 'PCI support' CONFIG_PCI
if [ "$CONFIG_PCI" = "y" ]; then
- bool ' PCI BIOS support' CONFIG_PCI_BIOS
- bool ' PCI direct access support' CONFIG_PCI_DIRECT
- if [ "$CONFIG_PCI_BIOS" = "n" -a "$CONFIG_PCI_DIRECT" = "n" ]; then
- define_bool CONFIG_PCI_BIOS "y"
- fi
+ choice ' PCI support type' \
+ "BIOS CONFIG_PCI_BIOS \
+ Direct CONFIG_PCI_DIRECT" BIOS
bool ' PCI quirks' CONFIG_PCI_QUIRKS
if [ "$CONFIG_PCI_QUIRKS" = "y" -a "$CONFIG_EXPERIMENTAL" = "y" ]; then
bool ' PCI bridge optimization (experimental)' CONFIG_PCI_OPTIMIZE
fi
bool ' Backward-compatible /proc/pci' CONFIG_PCI_OLD_PROC
===8<=== CUT ===>8===
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/