Hi Ivo

On Thu, 25 Oct 2007, Ivo van Doorn wrote:

quoted text
> 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.

Parag
-
unsubscribe notice
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/