Hi, let me first apologize for asking such a user-centric question on this mailing list, but I don't know any other place where I could find people captable of answering this question. I got a new Philips Speechmike Classic [1] that I need to get working under Linux. It's a dictation microphone that contains a mouse, a microphone/speaker combination and several buttons. First the good news: the integrated trackball (regular usb mouse driver) and microphone/speaker (snd-usb-audio) are working. What's missing is support for the buttons. I pasted the output of "lsusb -v" for the device at http://pastebin.com/m756b5f92 A hiddev device is created at /dev/hiddev0 and I get some input on that device by pressing the keys. I don't know if that is useful to you, but when I press a key I get that: $ sudo cat /dev/hiddev0 | hexdump 0000000 0003 ffa1 ff80 ffff 0004 ffa1 0000 0000 0000010 0004 ffa1 0000 0000 0004 ffa1 0000 0000 * 0000040 0004 ffa1 ff84 ffff 0003 ffa1 ff80 ffff 0000050 0004 ffa1 0000 0000 0004 ffa1 0000 0000 * 0000080 0004 ffa1 0000 0000 0004 ffa1 0004 0000 (the first two lines are onPress, the last three onRelease) I now have two questions: are there chances that the device is just a regular "keyboard" that is not recognized by the kernel as such? If yes, could I force the kernel to treat the device as "keyboard"? If not, what's the best way to get a working driver for it? Use libusb to write a user space driver for it? It's only 8 buttons, so I guess even I would be able to write something here, but I'd like to get it "done right", and I'm not exactly sure where to start. Thanks for your help, Philipp [1] http://www.dictation.philips.com/index.php?id=1436 -- 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
