On Sun, 26 Apr 2009, Philipp Wagner wrote: > I did that and uploaded the results at > > http://philipp.wagner.name/temp/speechmike-debug/ > > The messages-button* files are the dmesg output for one of the keys > each. The messages-plug-in.txt is the output when plugging the device in. > Is there anything you can see from that data? Thanks. The device seems to be violating HID specification in a non-trivial way. Could you please apply the debugging patch below and provide the very same output again? Also, what are the expected mappings of the buttons please (see the existing KEY_ macros in include/linux/input.h). diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c index ac8049b..3ef2a3e 100644 --- a/drivers/hid/usbhid/hid-core.c +++ b/drivers/hid/usbhid/hid-core.c @@ -891,6 +891,14 @@ static int usbhid_parse(struct hid_device *hid) dbg_hid_line(" %02x", (unsigned char) rdesc[n]); dbg_hid_line("\n"); + /* SPEECHMIKE DEBUG */ + if (rdesc[26] == 0x75 && rdesc[27] == 0x08 && + rdesc[28] == 0x95 && rdesc[29] == 0x09) { + printk(KERN_DEBUG "SPEECHMIKE DEBUG -- ALTERING REPORT DESCRIPTOR\n"); + rdesc[27] = 0x01; + rdesc[29] = 0x48; + } + ret = hid_parse_report(hid, rdesc, rsize); kfree(rdesc); if (ret) { -- 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
