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? I've tried to work-around the issue by created a user-space driver with libusb and uinput, but libusb fails to send events when there is moderate CPU utilization (I'm using this within MythTV and libusb just stops working when watching live TV). If the user-space driver is the only way to do what I want, then I will contact the libusb folks to see if they have a solution to that issue. I'd much rather get the kernel module driver working, though. Thanks ------------------------------------------------------------------------- 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
