mirror of
https://github.com/apache/nuttx.git
synced 2026-08-01 20:28:58 +00:00
b5382c5fb3
The keyboard driver documentation described the byte stream codec and nothing else. It never mentioned keyboard_register(), keyboard_event() or the event types, so somebody writing a driver had no way to find the interface that every keyboard in the tree actually uses. That omission has a cost that can be counted: six of the nine drivers that register a keyboard report only the press and release types and never the special ones, which means their arrow keys are silently dropped by any application that follows the contract. The header they would read to find out declares two of the four types. Document the contract, why the event type is what tells an arrow key from the character that shares its value, what to name the device, how to get a matrix keyboard working without writing a driver at all, and how to test the result with or without the hardware. Signed-off-by: Jorge Guzman <jorge.gzm@gmail.com> |
||
|---|---|---|
| .. | ||
| _extensions | ||
| _static | ||
| _templates | ||
| applications | ||
| components | ||
| contributing | ||
| debugging | ||
| faq | ||
| guides | ||
| implementation | ||
| introduction | ||
| logos | ||
| platforms | ||
| quickstart | ||
| reference | ||
| ReleaseNotes | ||
| standards | ||
| testing | ||
| .gitignore | ||
| conf.py | ||
| glossary.rst | ||
| index.rst | ||
| known-warnings.txt | ||
| legacy_README.md | ||
| make.bat | ||
| Makefile | ||
| Pipfile | ||
| Pipfile.lock | ||
| security.rst | ||
| substitutions.rst | ||