Re: [PATCH v4] Add virtio-input driver.

From
Vojtech Pavlik <hidden>
Date
2015-03-25 05:36:26
Also in
lkml
Reply to
Rusty Russell, 2015-03-25
On Wed, Mar 25, 2015 at 01:51:43PM +1030, Rusty Russell wrote:
Gerd Hoffmann [off-list ref] writes:
quoted
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.
I'm rather biased having designed it, but I'd say it's reasonable. It
certainly has limitations and design mistakes, but none are too bad.
One testimony to that Android has based its own Input API around it.
What's it used for?
For all human input devices, like keyboards, mice, touchscreens, etc. 
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?
A windows translation layer is fairly easy, people porting software from
Windows to Linux told me numerous times that adapting isn't hard. I also
believe that at least one of the BSD's has a compatible implementation
these days based on the fact that I was asked to allow copying the
headers in the past.

-- 
Vojtech Pavlik
Director SUSE Labs
Thread (5 messages) 5 messages, 4 authors, last reply 2015-03-26
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help