All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org
Cc: mst@redhat.com, David Herrmann <dh.herrmann@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:ABI/API" <linux-api@vger.kernel.org>,
	Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [PATCH v4] Add virtio-input driver.
Date: Wed, 25 Mar 2015 13:51:43 +1030	[thread overview]
Message-ID: <877fu5iwxk.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1427198927-1745-1-git-send-email-kraxel@redhat.com>

Gerd Hoffmann <kraxel@redhat.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@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.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Gerd Hoffmann <kraxel@redhat.com>,
	virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org
Cc: mst@redhat.com, David Herrmann <dh.herrmann@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list\:ABI\/API" <linux-api@vger.kernel.org>,
	"Vojtech Pavlik" <vojtech@suse.cz>
Subject: Re: [PATCH v4] Add virtio-input driver.
Date: Wed, 25 Mar 2015 13:51:43 +1030	[thread overview]
Message-ID: <877fu5iwxk.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1427198927-1745-1-git-send-email-kraxel@redhat.com>

Gerd Hoffmann <kraxel@redhat.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@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.

  parent reply	other threads:[~2015-03-25  3:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 12:08 [PATCH v4] Add virtio-input driver Gerd Hoffmann
2015-03-24 12:08 ` Gerd Hoffmann
2015-03-25  3:21 ` Rusty Russell
2015-03-25  3:21 ` Rusty Russell [this message]
2015-03-25  3:21   ` Rusty Russell
2015-03-25  5:36   ` Vojtech Pavlik
2015-03-25  5:36   ` Vojtech Pavlik
2015-03-26  1:53     ` Rusty Russell
     [not found]     ` <20150325053613.GA4572-IBi9RG/b67k@public.gmane.org>
2015-03-26  1:53       ` Rusty Russell
2015-03-26  1:53         ` Rusty Russell
2015-03-26  8:46 ` Michael S. Tsirkin
2015-03-26  8: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=877fu5iwxk.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=dh.herrmann@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=vojtech@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.