From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [PATCH 0/1] Add virtio-input driver.
Date: Thu, 19 Mar 2015 14:35:45 +0100 [thread overview]
Message-ID: <20150319141302-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1426756391-26585-1-git-send-email-kraxel@redhat.com>
On Thu, Mar 19, 2015 at 10:13:10AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> This patch adds a virtio driver for input devices.
>
> Specification:
> https://www.kraxel.org/cgit/virtio-spec/log/?h=virtio-input
> https://www.kraxel.org/virtio/virtio-v1.0-csprd03-virtio-input.html#x1-2640007
OK, I don't know which thread should I use for spec discussions.
Referring to that:
"See file:///usr/include/linux/input.h."
Is likely not present on many systems, or might not include
the info you refer to.
"type, code and value are filled according to the linux input layer
(evdev) interface"
Which version? How will non-linux guests know what to implement?
>
> Qemu patches;
> https://lists.gnu.org/archive/html/qemu-devel/2015-03/threads.html#03973
>
> Gerd Hoffmann (1):
> Add virtio-input driver.
>
> drivers/virtio/Kconfig | 10 ++
> drivers/virtio/Makefile | 1 +
> drivers/virtio/virtio_input.c | 313 ++++++++++++++++++++++++++++++++++++++
> include/uapi/linux/virtio_ids.h | 1 +
> include/uapi/linux/virtio_input.h | 65 ++++++++
> 5 files changed, 390 insertions(+)
> create mode 100644 drivers/virtio/virtio_input.c
> create mode 100644 include/uapi/linux/virtio_input.h
>
> --
> 1.8.3.1
next parent reply other threads:[~2015-03-19 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1426756391-26585-1-git-send-email-kraxel@redhat.com>
2015-03-19 13:35 ` Michael S. Tsirkin [this message]
2015-03-19 14:46 ` [Qemu-devel] [PATCH 0/1] Add virtio-input driver Gerd Hoffmann
2015-03-19 16:33 ` Michael S. Tsirkin
2015-03-19 17:05 ` Paolo Bonzini
2015-03-19 16:46 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150319141302-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).