Jiri Kosina wrote: > I am not really sure I understand very well. So you have the device the > provides some "crippled" implementation of USB and provides some HID > devices on top of it, and you would like to have this compliant with the > kernel Input/HID infrastructure? Yeah we can define it that way. It basically provides a low-speed USB port to chips that do not have a USB controller and PHY. Yes, it sounds disgusting, but sometimes it's the only way to use USB input devices to embedded systems that do not have USB connectivity. > If the devices are really HID (i.e. the protocol on the wire is proper HID > as defined by HID specification), you'd only need to implement a > specialized "transport" HID code for this transport protocol, and let the > HID core do the rest. Well those are standard USB keyboard and mice, so what goes on the wire is what is expected by those devices. > Currently there are implementations for USB and Bluetooth which you can > look at. Could you point me to a more specific example? Thank you Alessio -- 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
