Messages in this thread | | | Date | Wed, 9 Apr 2003 08:38:33 +0200 | From | Dominik Brodowski <> | Subject | Re: [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support |
| |
On Tue, Apr 08, 2003 at 05:05:53PM -0700, Jean Tourrilhes wrote: > 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.
Actually, I was unaware of this problem: etc/* of pcmcia-cs-3.2.3 only tells me about the orinoco_cs driver. And that's the only one I can find in kernel 2.5.67 as well.... However, for such cases there is already an override option in my patches: echo -n "driver_the_next_device_needs" > /sys/bus/pcmcia/settings/force_match
> > > 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.
i.e. a ->probe() callback?
Dominik - 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/
| |