From: Henrik Rydberg <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Chase Douglas <chase.douglas@canonical.com>,
Jiri Kosina <jkosina@suse.cz>, Ping Cheng <pingc@wacom.com>,
Chris Bagwell <chris@cnpbagwell.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2] input: Introduce device information ioctl
Date: Thu, 16 Dec 2010 08:43:02 +0100 [thread overview]
Message-ID: <4D09C306.4050207@euromail.se> (raw)
In-Reply-To: <201012151352.23229.dmitry.torokhov@gmail.com>
>>> As an example of how this would work for the
>>> touchpad/tablet/touchscreen triplet, there are two properties defined,
>>> INPUT_PROP_POINTER and INPUT_PROP_DIRECT. A touchpad is an indirect
>>> pointer device, a tablet is a direct pointer device, and the
>>> touchscreen is simply a direct device.
>>>
>>> What do you think?
>>
>> I must have missed the first version of this patch, but I give two
>> thumbs way up :). The detection code for touchpad/tablet/touchscreen in
>> xf86-input-evdev is large and unwieldy, and seemingly simple changes to
>> an input driver can cause incorrect interpretation. Having this
>> available should help quite a bit!
>>
>> Acked-by: Chase Douglas <chase.douglas@canonical.com>
>
> As long as we document that !pointer && !direct means "unknown" or
> "unspecified" so as to avoid having to update all devices at once that
> should be OK.
>
> We also need to wire up uinput.
Great, will cook a proper patch.
Thanks,
Henrik
next prev parent reply other threads:[~2010-12-16 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 19:20 [RFC v2] input: Introduce device information ioctl Henrik Rydberg
2010-12-15 21:16 ` Chase Douglas
2010-12-15 21:52 ` Dmitry Torokhov
2010-12-16 7:43 ` Henrik Rydberg [this message]
2010-12-16 0:29 ` Peter Hutterer
2010-12-16 0:43 ` Dmitry Torokhov
2010-12-16 13:57 ` Henrik Rydberg
2010-12-20 8:16 ` Peter Hutterer
2010-12-16 14:18 ` Henrik Rydberg
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=4D09C306.4050207@euromail.se \
--to=rydberg@euromail.se \
--cc=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=pingc@wacom.com \
/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).