Gerd Hoffmann [off-list ref] writes:
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and forwarding
incoming events to the linux input layer.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Is the input layer sane? I've never dealt with it, so I don't know.
What's it used for?
Imagine a future virtio standard which incorporates this. And a Windows
or FreeBSD implementation of the device and or driver. How ugly would
they be?
Thanks,
Rusty.