On Sat, 13 Sep 2008, Didier Moens wrote: > Sep 10 08:46:40 moewelstat1 kernel: input: Thrustmaster Thrustmaster force > feedback wheel as /class/input/input13 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0022 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0050 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0022 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0060 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0063 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0022 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0070 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0022 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0079 > Sep 10 08:46:40 moewelstat1 kernel: drivers/hid/usbhid/hid-tmff.c: ignoring > unknown output usage 000f0097 Hi, apparently, Thrustmaster has changed the report descriptor of the device a little bit. Probably also the protocol for this device is a little bit different. I have added Zinx to CC, as he wrote the original driver. For start, running hd in debugging mode (CONFIG_HID_DEBUG and modprobing 'hid' module with 'debug=2' parameter) and capturing output of a working session in windows might be good steps. -- Jiri Kosina SUSE Labs -- 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
