> Greg KH wrote:
> >Hm, in looking at this, I know the majority of people who want
> >CONFIG_HOTPLUG probably do not run with CONFIG_PCI_HOTPLUG as the
> >hardware's still quite rare. To force those people to keep
> around all
> >of the PCI quirks functions and tables after init happens, is a bit
> >cruel. I wonder if it's time to start having different subsystems
> >modify __devinit depending on their config variables.
>
> Are there PCI bridge cards that use all of those? For
> example, I thought that Triton was a series of Intel motherboard
> chipsets for 586 processors. Perhaps you only need to keep a
> few of those routines.
>
> Jung-Ik: perhaps you could to an lspci and an "lspci -n" on
> your machine when the bridge card is plugged in, which should provide
> enough information to determine which routines you really need to
> keep.
That sounds a quick fix for now but Greg's __pci_devinit seems to be the
right solution.
thanks,
J.I.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:33 EST