From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@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 15:46:44 +0100 [thread overview]
Message-ID: <1426776404.10990.10.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <20150319141302-mutt-send-email-mst@redhat.com>
On Do, 2015-03-19 at 14:35 +0100, Michael S. Tsirkin wrote:
> 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.
Dunno what the best way to deal with it is. Link to the version online
@ kernel.org instead maybe?
> "type, code and value are filled according to the linux input layer
> (evdev) interface"
>
> Which version?
Latest. As far I know there never ever have been incompatible changes
to the interface, and given this is userspace/kernel abi I don't expect
that to happen in the future.
> How will non-linux guests know what to implement?
There are some docs on the linux input layer and evdev events in
Documentation/input/ in the kernel tree.
cheers,
Gerd
next prev parent reply other threads:[~2015-03-19 14:46 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 ` [Qemu-devel] [PATCH 0/1] Add virtio-input driver Michael S. Tsirkin
2015-03-19 14:46 ` Gerd Hoffmann [this message]
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=1426776404.10990.10.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=mst@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).