On Fri, Jul 6, 2012 at 11:32 PM, Yuri Khan <yurivkhan@xxxxxxxxx> wrote: > When I add a usbhid option quirks=0x0738:0x4540:0x4 (so that usbhid does > not attempt to handle this device) and rebuild the xpad module with the > following patch, the device works as expected. Dmitry Torokhov, the > current maintainer of input drivers, suggested that I include a change > to add the usbhid quirk in my patch. Of course the good idea only ever comes after the fact. If I change usbhid to ignore this vendor:device unconditionally, then xpad should also always handle it regardless of interface class/subclass/protocol, right? -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html