From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Chris Bagwell <chris@cnpbagwell.com>,
Ping Cheng <pinglinux@gmail.com>,
Rafi Rubin <rafi@seas.upenn.edu>,
linux-input <linux-input@vger.kernel.org>,
Stephane Chatty <chatty@lii-enac.fr>,
Jiri Kosina <jkosina@suse.cz>,
Benjamin Tissoires <tissoire@cena.fr>,
Peter Hutterer <peter.hutterer@who-t.net>,
"X.Org Devel List" <xorg-devel@lists.freedesktop.org>
Subject: Re: EVIOC mechanism for MT slots
Date: Fri, 21 Jan 2011 01:22:01 -0800 [thread overview]
Message-ID: <20110121092200.GA24214@core.coreip.homeip.net> (raw)
In-Reply-To: <20110121091519.GA13565@polaris.bitmath.org>
On Fri, Jan 21, 2011 at 10:15:19AM +0100, Henrik Rydberg wrote:
> > This is really problematic when launching applications that rely on
> > evdev to work:
> > you click with the mouse emulation on your icon to launch the program
> > (one finger), and you start using your application with one finger
> > only (opening of a file for instance) -> you are in an unstable case
> > as the app does not know the slot state until you put another finger
> > on the screen.
> >
> > So I'm in favor of applying this patch Henrik submitted last May.
>
> Great, so there seems to be sufficient interest to warrant revisiting
> this. If you can find the patches, I will queue them in my tree. ;-)
>
> And if Dmitry concurs, perhaps we can even aim at 2.6.38.
>
The reason I objected in the first place is that the patch was a "nice
to have for completeness". Now that there are actual users needing this
data I have no issues with adding ioctl to retrieve this data.
Thanks.
--
Dmitry
prev parent reply other threads:[~2011-01-21 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 21:10 EVIOC mechanism for MT slots Rafi Rubin
2011-01-21 1:45 ` Ping Cheng
2011-01-21 3:57 ` Chris Bagwell
2011-01-21 7:58 ` Benjamin Tissoires
2011-01-21 9:15 ` Henrik Rydberg
2011-01-21 9:22 ` Dmitry Torokhov [this message]
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=20110121092200.GA24214@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=chatty@lii-enac.fr \
--cc=chris@cnpbagwell.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=pinglinux@gmail.com \
--cc=rafi@seas.upenn.edu \
--cc=rydberg@euromail.se \
--cc=tissoire@cena.fr \
--cc=xorg-devel@lists.freedesktop.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).