On Tue, 30 Mar 2010, Matthias Urlichs wrote: > The problem: I have a keyboard-faking scanner which is blacklisted in > usbhid: hid/hid-core.c: HID_USB_DEVICE(USB_VENDOR_ID_TENX, > USB_DEVICE_ID_TENX_IBUDDY1) > > Apparently, this is because the vendor is stupid and has re-used the USB > ID and descriptor for all kinds of scanner interfaces, not all of which > behave like a keyboard. What difference does that make? The ID doesn't matter; only the HID descriptor and report descriptors matter. > Mine does, however. Unfortunately, binding the thing to usbhid by way of > "echo USBPATH > /sys/bus/usb/drivers/usbhid/bind" fails, most probably > because the blacklist is still honored when doing that manually. > > So, is there a way to circumvent that blacklist? If usbhid can figure > out whether the probe was triggered via sysfs, this should be fairly > easy. There is no way to tell what triggered a probe. What happens if you simply remove the backlist entry? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
