On Friday 26 October 2007, Parag Warudkar wrote: > > Hi Ivo > > On Thu, 25 Oct 2007, Ivo van Doorn wrote: > > > I awknowledge the problem, but the solution cannot be found in the USB ID's > > listed in the driver. The bug is the manufacturer who changed chipset while > > keeping the USB ID the same. > > There are 2 possible ways around this: hacking the module loader so > > it continues searching for a different driver when the first driver > > indicates > > that it cannot control the device. > > Or the easiest way, just blacklist rt2500usb if you are sure you need the > > rt73 driver. > > Thanks for the heads up - I think you have a good idea - there should be > an interface between the loader and module to specify conditions like this. > > I will see if I can generate interest in that idea and hack up something > along the lines of your suggestion.
Well it could be something quite simple, in the module loader it is looping through all modules to look for a device with the correct USB/PCI ID. Currently, after the first occurence it loads the module and doesn't continue, it should perhaps be relatively easy that it checks if the driver returned -ENODEV and continues looping to search for another driver. Ivo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
