Luis R. Rodriguez wrote: > I had done some something similar for ar9170 a while back [1] when > adding AVM FRITZ support to ar9170 and then got complaints from Marcel > on this approach since it requires synching the PCI device IDs in two > places. I frankly don't care how we do this but we should try to at > least stick to one way of doing this. > > [1] http://osdir.com/ml/linux-wireless/2009-05/msg01219.html I did look at using the device_id table (using USB_DEVICE_VER), but our case is like this: * for prodId, version 2.2 load foo_1_1.fw * for prodId, version everything else, load foo.fw This requires a bit of handling in the driver, hence this patch. But thinking about it, will this work ? USB_DEVICE_VER(vend, 0x7010, 2, 2); [set .driver_info to "foo_1_1.fw] USB_DEVICE(vend, 0x7010); [set .driver_info to "foo.fw"] That is, will the second registration be the fallback case in case bcdLo and bcdHi are _anything_ other than 2.2 ? Sujith -- 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
