RFC input: rewrite qemu input layer
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest15 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/15 | console: export QemuConsole index, width, heightinclude/ ui/ | +27 | 0 replies | |
| 2/15 | input: rename file to legacyui/ ui/ | +1 | 0 replies | |
| 3/15 | input: define event types using qapiqapi-schema.json | +29 | 2 replies | |
| 4/15 | input: add core bits of the new input layerinclude/ ui/ ui/ | +116 | 0 replies | |
| 5/15 | input: keyboard: add helper functions to coreinclude/ ui/ | +22 | 0 replies | |
| 6/15 | input: keyboard: switch legacy handlers to new coreui/ | +44 | 0 replies | |
| 7/15 | input: keyboard: switch qmp_send_key() to new core.ui/ | +2 | 0 replies | |
| 8/15 | input: keyboard: switch gtk ui to new coreui/ | +4 | 0 replies | |
| 9/15 | input: keyboard: switch sdl ui to new core [wip]ui/ | +10 | 0 replies | |
| 10/15 | input: mouse: add helpers functions to coreinclude/ ui/ | +85 | 0 replies | |
| 11/15 | input: mouse: add graphic_rotate supportui/ | +33 | 2 replies | |
| 12/15 | input: mouse: add qemu_input_is_absolute()include/ ui/ | +9 | 1 reply | |
| 13/15 | input: mouse: switch legacy handlers to new coreui/ | +63 | 0 replies | |
| 14/15 | input: mouse: switch gtk ui to new coreui/ | +19 | 0 replies | |
| 15/15 | input: mouse: switch sdl ui to new coreui/ | +34 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Qemu-devel] [RFC PATCH 00/15] input: rewrite qemu input layer
Hi,
This patch series is the first draft of a input layer rewrite. New core code is largely in place. There is some windup for the legacy functions, to keep things working while switching over users one by one.
Some ui code is converted to make clear how the new input layer should be used.
No work on the device emulation side of things yet.
Main motivation for this is multihead support. Thats why QemuConsole is passed everythere, even though the code doesn't use it (yet). But some day the input layer has the should be able to process/route events depending on the source.
Easy monitor integration is on the radar too, even though none if this is coded up yet. I wanna test the data structures more before even thinking about exposing them via qmp.
In general the new way of handling events should more flexible and be easier to extend than the old code we have right now. We might want add touch support for example ...
Reviews? Comments?
cheers,
Gerd
Gerd Hoffmann (15):
console: export QemuConsole index,width,height
input: rename file to legacy
input: define event types using qapi
input: add core bits of the new input layer
input: keyboard: add helper functions to core
input: keyboard: switch legacy handlers to new core
input: keyboard: switch qmp_send_key() to new core.
input: keyboard: switch gtk ui to new core
input: keyboard: switch sdl ui to new core [wip]
input: mouse: add helpers functions to core
input: mouse: add graphic_rotate support
input: mouse: add qemu_input_is_absolute()
input: mouse: switch legacy handlers to new core
input: mouse: switch gtk ui to new core
input: mouse: switch sdl ui to new core
include/ui/console.h | 3 + include/ui/input.h | 50 ++++ qapi-schema.json | 29 +++ ui/Makefile.objs | 2 +- ui/console.c | 24 ++ ui/gtk.c | 77 ++---- ui/input-legacy.c | 650 +++++++++++++++++++++++++++++++++++++++++++++++++++ ui/input.c | 627 +++++++++++-------------------------------------- ui/sdl.c | 88 +++---- 9 files changed, 965 insertions(+), 585 deletions(-) create mode 100644 include/ui/input.h create mode 100644 ui/input-legacy.c
Signature · 1 line
1.8.3.1