On Tue, 21 Apr 2009, Alessio Sangalli wrote: > Hi I would need a hint what is best to do; I have an embedded device > that can do a "soft" implementation of USB for embedded applications. > The aim is to be compatible with low-speed HID USB devices. > > The fact is, it does not implement a full USB stack but only > point-to-point communication with the aforementioned devices. I know it > sounds weird but it's more like a "PS/2" port than a USB thing. > > Now, I have a generic character device driver that can read keyboard and > mouse data. Of course I get what a USB device would send when you press > keys etc. > > How do you think it would be the best way to integrate it with the input > subsystem? 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? 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. Currently there are implementations for USB and Bluetooth which you can look at. Or maybe I just misunderstood your situation completely? -- 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
