From: Henrik Rydberg <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Ping Cheng <pinglinux@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Mika Kuoppala <mika.kuoppala@nokia.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
Benjamin Tissoires <tissoire@cena.fr>,
Stephane Chatty <chatty@enac.fr>,
Rafi Rubin <rafi@seas.upenn.edu>,
Michael Poole <mdpoole@troilus.org>
Subject: Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3)
Date: Fri, 21 May 2010 19:49:42 +0200 [thread overview]
Message-ID: <4BF6C7B6.2020008@euromail.se> (raw)
In-Reply-To: <20100521174140.GA23155@core.coreip.homeip.net>
Dmitry Torokhov wrote:
>
> I guess this is where our disconnect lies as when I am looking at the
> event names I view all *_MT_* events as related to the multitouch
> protocol handling.
>
Yes. It is true that slot control is MT related, but I am looking at this from
the perspective of future expansions like KEY_MT, KEY_REL, and such, finding a
way to signal to user space which events are handled via slots. If we had
ABS_MT_SLOT, we would most likely get applications which store ABS_MT_SLOT as an
attribute of the slot together with ABS_MT_POSITION_X, ABS_MT_TOUCH_MAJOR, etc,
which is just not right. So the proposal is ABS_SLOT. May we have your verdict,
please. :-)
Henrik
next prev parent reply other threads:[~2010-05-21 17:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 15:55 [PATCH 1/2] input: mt: Introduce MT event slots (rev 4) Henrik Rydberg
2010-05-21 15:55 ` [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3) Henrik Rydberg
2010-05-21 16:30 ` Ping Cheng
2010-05-21 16:36 ` Henrik Rydberg
2010-05-21 16:52 ` Dmitry Torokhov
2010-05-21 16:56 ` Henrik Rydberg
2010-05-21 17:22 ` Dmitry Torokhov
2010-05-21 17:29 ` Henrik Rydberg
2010-05-21 17:41 ` Dmitry Torokhov
2010-05-21 17:49 ` Henrik Rydberg [this message]
2010-05-22 3:52 ` Ping Cheng
2010-05-22 7:08 ` Henrik Rydberg
2010-05-22 9:11 ` Henrik Rydberg
2010-05-22 9:33 ` Rafi Rubin
2010-05-22 10:38 ` Henrik Rydberg
2010-05-22 14:46 ` Chase Douglas
2010-05-22 17:47 ` Henrik Rydberg
2010-05-22 20:52 ` Chase Douglas
2010-05-22 20:56 ` Dmitry Torokhov
2010-05-22 21:09 ` Henrik Rydberg
2010-05-22 20:16 ` Dmitry Torokhov
2010-05-22 21:15 ` 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=4BF6C7B6.2020008@euromail.se \
--to=rydberg@euromail.se \
--cc=akpm@linux-foundation.org \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdpoole@troilus.org \
--cc=mika.kuoppala@nokia.com \
--cc=peter.hutterer@who-t.net \
--cc=pinglinux@gmail.com \
--cc=rafi@seas.upenn.edu \
--cc=tissoire@cena.fr \
/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).