[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877fu5iwxk.fsf@rustcorp.com.au>
Date: Wed, 25 Mar 2015 13:51:43 +1030
From: Rusty Russell <rusty@...tcorp.com.au>
To: Gerd Hoffmann <kraxel@...hat.com>, virtio-dev@...ts.oasis-open.org,
virtualization@...ts.linux-foundation.org
Cc: mst@...hat.com, David Herrmann <dh.herrmann@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Gerd Hoffmann <kraxel@...hat.com>,
open list <linux-kernel@...r.kernel.org>,
"open list\:ABI\/API" <linux-api@...r.kernel.org>,
"Vojtech Pavlik" <vojtech@...e.cz>
Subject: Re: [PATCH v4] Add virtio-input driver.
Gerd Hoffmann <kraxel@...hat.com> 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@...hat.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists