Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 8 Apr 2003 17:05:53 -0700 | Subject | Re: [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support | From | Jean Tourrilhes <> |
| |
On Tue, Apr 08, 2003 at 06:56:12PM -0400, Jeff Garzik wrote: > > > Example : > > Lucent/Agere Orinoco wireless card : > > manfid 0x0156,0x0002 > > possible drivers : wlan_cs ; orinoco_cs > > Intersil PrismII and clones (Linksys, ...) : > > manfid 0x0156,0x0002 > > possible drivers : prism2_cs ; hostap_cs > > > > Please explain me in details how your stuff will cope with the > >above, and how to make sure the right driver is loaded in every case > >and how user can control this. > > If your scheme can't cope with the simple real life example > >above (I've got those cards on my desk, and those drivers on my disk), > >then it's no good to me. > > These cases already exist for PCI, so pcmcia behavior should follow what > the kernel does when the PCI core sees such. > > Jeff
I've never heard of a case of PCI-ID collision between two different manufacturer, so I need to update myself ;-) I was already burnt by this mess, as many IrDA users get confused when ir-usb loads instead of irda-usb, so my experience so far in handling those case has not been very positive. But, I trust you now have things under control ;-)
Have fun...
Jean - 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/
| ![\](/images/icornerr.gif) |