On Sat, Dec 13, 2014 at 2:56 PM, Jiri Kosina <jkosina@xxxxxxx> wrote: > On Fri, 12 Dec 2014, Andy Lutomirski wrote: > >> It's roughly ISO7816-3. For the uninitiated (and the ISO7816 standard >> is amazingly vague), that means that the application sends a short >> (<64kB) binary request to the device (with a type, two "parameters", >> and a payload), and the device answers with exactly one reply packet >> that has two bytes of status and a payload. These requests and >> replies are fragmented into multiple HID reports. > > Sorry for taking one (or maybe even more) step back, but what makes this > thing even "HID device"? > > Yes, it interacts with human beings, but are the operations it's doing > covered by HID specification (at least in a "does it have HID descriptor" > sense)? It's not really completely clear to me at this point. It has a HID descriptor, it's recognized by the HID stack, it understands SET_REPORT, and it generates async HID reports. Hidraw is willing to talk to it and, in fact, Chromium talks to it using hidraw (ugh). It's also supposed to be *enumerated* by reading the HID descriptor. There are multiple vendors of these things, and the USB descriptor doesn't seem to have anything in it to identify the device. I think that's the full extent to which it's a HID device. --Andy > > Thanks, > > -- > Jiri Kosina > SUSE Labs -- Andy Lutomirski AMA Capital Management, LLC -- 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
