Akihiko Odaki 184c07600d ui/input: Use Linux key codes for internal key events ...

Linux input key codes are a better internal representation than
QKeyCode:

- With Linux input key codes as the internal representation, keys
  previously lost solely because the middle layer between event sources
  and sinks used QKeyCode will be preserved, since Linux key codes
  cover all keys that those sources and sinks use. For example,
  KEY_KPJPCOMMA cannot be represented with QKeyCode, but it is widely
  supported by event sources and sinks since it is included in linux,
  atset1, atset2, usb, x11, osx, qnum (derived from atset1),
  xorgxquartz, and xorgevdev (derived from linux).

- They make it possible to pass through Linux host key codes to Linux
  guests to preserve all key inputs.

- They simplify consumers by avoiding QKeyCode aliases, namely
  asterisk/kp_multiply and sysrq/print.

This matches the approach used by virtio and Xen.

Signed-off-by: Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-ID: <20260520-input-v3-4-7c9e4c7abe34@rsg.ci.i.u-tokyo.ac.jp>

2026-05-25 01:00:54 +04:00

..

ebpf

ebpf: Add a separate target for skeleton

2024-06-04 15:14:26 +08:00

i386

misc: Clean up includes

2026-01-22 11:23:31 +00:00

qemu-vnc

ui/input: Use Linux key codes for internal key events

2026-05-25 01:00:54 +04:00

meson.build

virtiofsd: Remove build and docs glue

2023-02-16 18:15:08 +00:00