Messages in this thread | | | Subject | Re: [PATCH] pci bridge class code | From | Alan Cox <> | Date | 30 May 2003 10:44:14 +0100 |
| |
On Iau, 2003-05-29 at 21:40, Russell King wrote: > On Thu, May 29, 2003 at 01:17:42PM -0700, Mark Haverkamp wrote: > > This adds pci-pci bridge driver model class code. Entries appear in > > /sys/class/pci_bridge. > > Hmm. Ok. > > How do you propose to handle the following case: > > Mobility Electronics supply a Cardbus to PCI bridged "docking station" > which has a PCI-PCI bridge on with vendor stuff above 0x40. It appears > as a standard PCI-PCI bridge; the only specific identifying information > are the device and vendor IDs. How can I guarantee that a driver I > write for this device will be picked up in preference to your driver. > > (Given that your driver would probably be always loaded, and my driver > could well be a loadable module.)
The same is true of serveral hot docking bridges such as the one on the IBM TP600 and also of other devices which happen to be both a PCI-PCI bridge and have other magic stuck on them.
- 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/
| |