Technically, interrupts are still often involved… just from the USB controller on the state of the polling instead of the keyboard directly on a keypress
Some keyboards implement the USB Boot Keyboard profile specified in the USB Device Class Definition for Human Interface Devices (HID) v1.11 and are explicitly configured to use the boot protocol. These are limited to 6-key rollover (6KRO) and will interrupt the CPU every time the keyboard is polled (even if there is no state change) unless the USB controller is programmed to tell the keyboard to respond with negative acknowledgments, which the USB controller discards in hardware without interrupting the CPU, when there are no state changes to report
So if i created my own keyboard from scratch on a open hardware microcontroller, could i implement this?
There’s also the case of Bluetooth dongle keyboards not working in UEFI (except that one) but USB always do. Is it this or just the UEFI not having drivers?
Technically, interrupts are still often involved… just from the USB controller on the state of the polling instead of the keyboard directly on a keypress
https://en.wikipedia.org/wiki/USB_human_interface_device_class#Keyboards
So if i created my own keyboard from scratch on a open hardware microcontroller, could i implement this?
There’s also the case of Bluetooth dongle keyboards not working in UEFI (except that one) but USB always do. Is it this or just the UEFI not having drivers?