On Sat, 14 Apr 2007, Greg KH wrote:
Because the hid driver grabs the device first as it was registered first with the kernel. Either disable the hid driver, or add your specific device type to the blacklist in the hid driver. Or manually bind and unbind the device from the driver and to your new driver by using the sysfs bind and unbind files.
In addition to what Greg wrote, there is also upcoming feature (hopefully for 2.6.22) that will allow for on-the-fly modification of hid quirks list, so you'd be able to put your device on hid_blacklist with HID_QUIRK_IGNORE in runtime.
But before this is merged, unbinding usbhid from your device from sysfs and/or recompiling kernel with modified hid_blacklist are options suitable for you.
-- Jiri Kosina -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
