On Thu, Sep 3, 2009 at 3:27 PM, Johannes Berg<johannes@xxxxxxxxxxxxxxxx> wrote: > On Thu, 2009-09-03 at 15:27 +0300, Amit Kucheria wrote: >> On 09 Sep 03, Ivo Van Doorn wrote: >> > > USB_DEVICE(0x148f, 0x2573) is served by the rt73usb driver where it is already >> > > defined. Remove it from rt2500usb. >> > > >> > > Signed-off-by: Amit Kucheria <amit.kucheria@xxxxxxxxxxxxx> >> > > Cc: Ivo van Doorn <IvDoorn@xxxxxxxxx> >> > >> > NACK >> > >> > Users have reported that this is a valid rt2500usb ID. You can thank the >> > manufacturer of the dongle to produce dongles with the same USB ID but >> > with different chipsets. >> > >> > Ivo >> >> Interesting. On my laptop, without this patch both the drivers are loaded >> (lsmod), rt2500usb aborts without allocating a device successfully but I am >> unable to associate to the AP. > > Sounds like the detection logic is somehow messing with the device, or > rt2500usb isn't actually freeing the device for rt73usb to bind? That would be odd, I believe it is working with other devices with duplicate ID's where first rt2500usb is loaded and then rt73usb. As far as connecting to the device, the first thing rt2x00 does is reading the EEPROM and checking the chipset. So no registers are being written which could upset a rt73usb device. Ivo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
