From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
"Michael S. Tsirkin" <mst@redhat.com>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
David Herrmann <dh.herrmann@gmail.com>
Subject: Re: [virtio-dev] Re: [PATCH v3] Add virtio-input driver.
Date: Tue, 24 Mar 2015 09:05:18 -0700 [thread overview]
Message-ID: <20150324160518.GA34117@dtor-ws> (raw)
In-Reply-To: <1427210714.18768.23.camel@nilsson.home.kraxel.org>
On Tue, Mar 24, 2015 at 04:25:14PM +0100, Gerd Hoffmann wrote:
> On Di, 2015-03-24 at 15:14 +0100, Michael S. Tsirkin wrote:
> > On Tue, Mar 24, 2015 at 02:37:24PM +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > > input layer checks it and ignores events not supported (according to the
> > > > > support bitmaps).
> > > >
> > > > Right but support bitmaps come from host too, no?
> > >
> > > Yes, but the driver will not set invalid bits (bitcount argument for the
> > > virtinput_cfg_bits() function is the number of valid bits of the
> > > specific bitmap).
> > >
> > > cheers,
> > > Gerd
> > >
> > >
> > >
> >
> > Question: does linux ever get such events from userspace
> > as opposed to sending them to userspace?
>
> Yes, it's possible using the userspace input driver
> (CONFIG_INPUT_UINPUT)
No, not through uinput (as from kernel POV uinput is also a driver), but
users can write into evdev.
Sending unknown codes is OK: events of unknown type will be dropped by
the input core, unknown event codes will be passed on; users not
recognizing event code should simply ignore it.
Thanks.
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org,
David Herrmann <dh.herrmann@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
open list <linux-kernel@vger.kernel.org>,
"open list:ABI/API" <linux-api@vger.kernel.org>
Subject: Re: [virtio-dev] Re: [PATCH v3] Add virtio-input driver.
Date: Tue, 24 Mar 2015 09:05:18 -0700 [thread overview]
Message-ID: <20150324160518.GA34117@dtor-ws> (raw)
In-Reply-To: <1427210714.18768.23.camel@nilsson.home.kraxel.org>
On Tue, Mar 24, 2015 at 04:25:14PM +0100, Gerd Hoffmann wrote:
> On Di, 2015-03-24 at 15:14 +0100, Michael S. Tsirkin wrote:
> > On Tue, Mar 24, 2015 at 02:37:24PM +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > > input layer checks it and ignores events not supported (according to the
> > > > > support bitmaps).
> > > >
> > > > Right but support bitmaps come from host too, no?
> > >
> > > Yes, but the driver will not set invalid bits (bitcount argument for the
> > > virtinput_cfg_bits() function is the number of valid bits of the
> > > specific bitmap).
> > >
> > > cheers,
> > > Gerd
> > >
> > >
> > >
> >
> > Question: does linux ever get such events from userspace
> > as opposed to sending them to userspace?
>
> Yes, it's possible using the userspace input driver
> (CONFIG_INPUT_UINPUT)
No, not through uinput (as from kernel POV uinput is also a driver), but
users can write into evdev.
Sending unknown codes is OK: events of unknown type will be dropped by
the input core, unknown event codes will be passed on; users not
recognizing event code should simply ignore it.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-03-24 16:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 7:32 [PATCH v3] Add virtio-input driver Gerd Hoffmann
2015-03-24 7:32 ` Gerd Hoffmann
2015-03-24 10:26 ` Gerd Hoffmann
[not found] ` <1427182321-19451-1-git-send-email-kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-03-24 10:26 ` Gerd Hoffmann
2015-03-24 10:26 ` Gerd Hoffmann
2015-03-24 10:40 ` Michael S. Tsirkin
2015-03-24 10:40 ` Michael S. Tsirkin
2015-03-24 10:48 ` Michael S. Tsirkin
2015-03-24 10:48 ` Michael S. Tsirkin
2015-03-24 10:36 ` Michael S. Tsirkin
2015-03-24 11:46 ` [virtio-dev] " Gerd Hoffmann
2015-03-24 11:46 ` Gerd Hoffmann
2015-03-24 13:02 ` Michael S. Tsirkin
2015-03-24 13:02 ` Michael S. Tsirkin
2015-03-24 13:37 ` Gerd Hoffmann
[not found] ` <20150324135908-mutt-send-email-mst-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-03-24 13:37 ` Gerd Hoffmann
2015-03-24 13:37 ` Gerd Hoffmann
2015-03-24 14:14 ` Michael S. Tsirkin
2015-03-24 15:25 ` Gerd Hoffmann
2015-03-24 15:25 ` Gerd Hoffmann
2015-03-24 16:05 ` Dmitry Torokhov [this message]
2015-03-24 16:05 ` Dmitry Torokhov
2015-03-24 14:14 ` Michael S. Tsirkin
2015-03-24 16:23 ` Dmitry Torokhov
2015-03-24 16:23 ` Dmitry Torokhov
2015-03-24 17:22 ` Michael S. Tsirkin
2015-03-24 17:22 ` Michael S. Tsirkin
2015-03-24 17:28 ` Dmitry Torokhov
2015-03-24 17:28 ` Dmitry Torokhov
2015-03-25 5:36 ` Michael S. Tsirkin
2015-03-25 5:36 ` Michael S. Tsirkin
2015-03-24 10:36 ` 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=20150324160518.GA34117@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=dh.herrmann@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 \
/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.