3 ms·
It was. HID is a depressingly complicated specification though, and split the keyboard protocol in half: there is a "boot" protocol, which is designed to be si
by ajross 7y ago
It was. HID is a depressingly complicated specification though, and split the keyboard protocol in half: there is a "boot" protocol, which is designed to be simpler for firmware to implement, and a full event protocol. The latter looks exactly like you'd expect such a thing to look like, with arbitrary up/down events reportable independently for as many keys as you want to declare.
But the boot protocol has a six key limit, so that's what many devices support.
- magicalhippo 7y ago> with arbitrary up/down events reportable independently for as many keys as you want to declare In "Appendix C - Keyboard Implementation" in the "USB Device Class Definition" document[1], it says: "The following are the design requirements for USB keyboards: - Non-modifier keys must be reported in Input (Array, Absolute) items. Reports must contain a list of keys currently pressed and not make/break codes (relative data)." Of course you could make some HID device which has relative key events, but would the OS then recognize it as a keyboard? [1]: https://www.usb.org/document-library/device-class-definition-hid-111 https://www.usb.org/document-library/device-class-definition...