Dynamic USB device IDs
Greg Kroah-Hartman has posted a simple patch which should help fix this situation. With the patch in place, each USB driver gets a new sysfs attribute (new_id). If a system administrator writes two values (the vendor and product ID numbers reported by the device) to that attribute, those numbers form a new device ID associated with the driver. Immediately after the write, the driver will recognize the device, and everybody will be happy. No changes to the drivers themselves are necessary. Of course, one could create confusion by associating a device with an inappropriate driver, but a bit of attention should suffice to avoid that problem.
This patch came out a bit late for 2.6.15, so it is more likely to show up
in 2.6.16 or thereafter.
Index entries for this article | |
---|---|
Kernel | Device drivers |
Kernel | USB |
Posted Nov 23, 2005 11:42 UTC (Wed)
by jcm (subscriber, #18262)
[Link] (2 responses)
Jon.
Posted Nov 24, 2005 13:45 UTC (Thu)
by hadess (subscriber, #24252)
[Link] (1 responses)
Posted Nov 24, 2005 14:09 UTC (Thu)
by jcm (subscriber, #18262)
[Link]
Sure, we all recompile our kernels every 10 minutes, but in the real world where there are a million people stuck on some $version of a distro, it'd be real nice if we could have it work with newer devices with such a simple hack rather than have them jump through too many hoops.
The average user isn't going to drop a new device id table entry to lkml :-)
Jon.
It'd be nice to see more of this kind of thing happening. Projects like DKMS already strive to make it easier to have devices detected and "just work" but this (semi obvious) patch helps more advanced users and admins to quickly get a device just installed. Perhaps this needs a userspace helper to allow a user to do this graphically.Dynamic USB device IDs
No. The point is to make the driver work "right now". It's something that you can already do with XFree96/X.org (using the DeviceID option IIRC), and with some kernel drivers (mainly storage ones).Dynamic USB device IDs
Having the driver work straight away means that you can test it without recompiling a kernel. Then you should drop a mail for the ID to be added properly. It's just a work-around.
I understand. My point is that there's nothing to stop DKMS or some other project from using this new API to facilitate getting devices to work either.Dynamic USB device IDs