- Nov 10, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
These are what we really want for SDL and Wine: they're broadly equivalent to the udev ID_INPUT_FOO properties, and identify which devices are desired at a high level. Also add test coverage for the device-type-guessing heuristic. Thanks to various people in Collabora, Codeweavers and #debian-uk for providing `sudo evemu-describe` output for their devices. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This is the official way to determine what an input device is, at the kernel level. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The name is to leave space for "type flags" (joystick, etc.) later. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Wine/Proton needs these for some of its HID functionality. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This includes: * a public interface implemented by input device monitors * a public interface to be implemented by the input devices they signal * a mock implementation for unit-testing * a unit test for the API * a simple implementation in terms of inotify on /dev * a monitor that can print input devices in JSON format on stdout, and optionally monitor them Implementations in terms of udev, SDL, or a portal service are not yet included. Details of the devices, beyond their paths in /dev and /sys, are also not included. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-