On Thu, Jan 28, 2010 at 07:10:17PM +0100, Simon Richter wrote: > Hi, > > I have a HID device that declares itself as a keyboard, but isn't, which > I'd like to use under Linux. This is because being a HID device was the only way to write userspace Windows code to control USB devices until very recently. So lots of manufacturers created "fake" HID devices. It's a mess. > I can see three options: > > - Add an IGNORE quirk to the table, and use the device via the > endpoints. Yup, I recommend this one. And then write either a new kernel driver, or a userspace program using libusb to talk to the device. What type of device is this really? > - Invent a new quirk that prevents the device from being connected to > anything but hidraw. If you really want to send HID commands to it. Does it accept them? Odds are, it doesn't. > - Add a new hidraw ioctl that disconnects all other report sinks. > > Option 3 could possibly be combined with option 2 to form a more generic > solution, but is obviously the most intrusive approach. > > Which way should I go? See above. thanks, greg k-h -- 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
