nuttx-apps/examples/lvglterm
Jorge Guzman 47b3f92f9d examples/lvglterm: read any keyboard through one input path
The terminal had three input sources to choose from, and its own help
text explained why:  the physical keyboard options "differ in the data
the keyboard device delivers on read(), so pick the one that matches the
hardware".  That is the abstraction leaking.  A user had to know that
the keyboard was USB rather than a matrix in order to compile the
terminal, and swapping one for the other meant rebuilding.

There are two sources now, touch and physical, and the physical one
reads any keyboard registered with keyboard_register().  Which format
arrives is decided by INPUT_KEYBOARD_BYTESTREAM, a property of the build
rather than of the hardware, so the terminal no longer asks.

Cursor keys reported as special events scroll the terminal, which is
what a driver following the current contract sends.  The out of band
codes that the M5Stack Cardputer reports as ordinary presses are still
honoured, so that board keeps working until its driver is converted.

Signed-off-by: Jorge Guzman <jorge.gzm@gmail.com>
2026-08-02 18:36:37 +08:00
..
CMakeLists.txt examples/lvglterm: add USB HID keyboard input with cursor scrolling 2026-07-07 09:52:42 +08:00
Kconfig examples/lvglterm: read any keyboard through one input path 2026-08-02 18:36:37 +08:00
lvglterm.c examples/lvglterm: add USB HID keyboard input with cursor scrolling 2026-07-07 09:52:42 +08:00
lvglterm.h examples/lvglterm: support physical keyboard input 2026-07-03 09:16:58 -03:00
lvglterm_kbd.c examples/lvglterm: read any keyboard through one input path 2026-08-02 18:36:37 +08:00
lvglterm_touch.c examples/lvglterm: support physical keyboard input 2026-07-03 09:16:58 -03:00
Make.defs examples: migrate to SPDX identifier 2024-12-30 18:02:50 +08:00
Makefile examples/lvglterm: add USB HID keyboard input with cursor scrolling 2026-07-07 09:52:42 +08:00