[PATCH RFC 0/5] Xephyr input hotplugging support and other additions for single-GPU multiseat

[Laércio de Sousa]

This patch series provides some missing parts for completing
single-GPU multiseat support for Xephyr.

Patches 1, 2, and 5 provide new command-line options to make it
easier to launch Xephyr directly from display manager, rather
than from within a user session.

Patch 4 fixes an issue where Xephyr keyboards' LEDs are not toggled
when NumLock, CapsLock, and ScrollLock are pressed.

Patch 3 is the most significant one, which introduces input hotplugging
support with udev backend. It still have some issues, and I need your
help for fixing them. In my tests, unplugging and replugging a USB keyboard
works fine, but Xephyr crashes when I unplug a USB mouse. I suspect
it may be related to the fact that a same mouse exposes two device nodes
(/dev/input/event* and /dev/input/mouse*), which only one of them is grabbed
by Xephyr. Maybe my DeleteInputDeviceRequest() implementation in kdrive.c
needs improvements.

Laércio de Sousa (4):
  ephyr: allow passing explictly host X server display number and/or
    authorization file path
  ephyr: ignore "-sharevts" and "-layout seatXXXX" command-line options
  kdrive: introduce input hotplugging support (udev backend provided)
    (#33140)
  kdrive: add options to set default XKB properties

Mikhail Krivtsov (1):
  kdrive: update evdev keyboard LEDs (#22302)

 hw/kdrive/ephyr/ephyrinit.c |  26 ++++++++++
 hw/kdrive/linux/evdev.c     |  11 +++--
 hw/kdrive/src/Makefile.am   |   2 +
 hw/kdrive/src/kdrive.c      |  81 +++++++++++++++++++++++++++++++
 hw/kdrive/src/kinput.c      | 114 +++++++++++++++++++++++++++++++++++++++-----
 5 files changed, 220 insertions(+), 14 deletions(-)

-- 
2.2.0