> Hello,
>
> In 2.1.132 I've found the following patch:
>
> @@ -39,6 +40,9 @@
> 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
> bool ' PCI quirks' CONFIG_PCI_QUIRKS
> if [ "$CONFIG_PCI_QUIRKS" = "y" -a "$CONFIG_EXPERIMENTAL" = "y" ]; then
> bool ' PCI bridge optimization (experimental)' CONFIG_PCI_OPTIMIZE
>
> 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.
If really we want a PCI config method to be selected in such a situation,
then, the best one is PCI DIRECT, in my opinion, at least for x386
platforms. The PCI BIOS should be considered as some work-around for too
broken PCI chipsets we just donnot want to deal with.
Gerard.
-
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/