On Wed, Dec 20, 2006 at 11:24:03AM -0800, chaoslink wrote: > I'm trying to write a custom driver for an HID Keyboard/Mouse from a > specific vendor. > > However, my "probe()" function is never called. I am specifying the > correct vendor and product ID, even "hotplug" shows that my driver > should be loaded for this device. It looks like "probe()" on the > built-in kernel driver is being called prior to my own and reading the > code it appears that probe'ing stops at the first matching driver. > > How do I rectify this? I don't want to remove the built-in driver > because I still want to use it for another generic USB keyboard and > mouse at the same time. Is there any way to set device driver probe > order to ensure that "probe()" is called first for my driver module?
Add your vendor/product id to the HID blacklist so it doesn't bind to the device. If you look, there are a number of entries in there for this very reason :) Hope this helps, greg k-h ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
