Before this commit the driver failed to load if it didn't create
a HID report descriptor for at least one device. The host evdev
device connected to the VM may be arbitrarily obscure and not being
able to drive it should not be an error condition.
In general, virtio-input is a best-effort driver. It ignores what
it doesn't understand, which includes ignoring everything if the
evdev device description doesn't make sense.
Signed-off-by: Ladi Prosek <[email protected]>
The driver now reads the EV_KEY and EV_REL config from the device
and builds an HID report descriptor describing the capabilities
(number of buttons, axes, wheels) of the mouse device. Also being
built is a smaller data structure used to transform EVDEV events
to HID reports at run-time.
Mouse is still the only supported input device class.
Viktor Prutyanov