From: Rafi Rubin <rafi@seas.upenn.edu>
To: Ping Cheng <pinglinux@gmail.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Dmitry Torokhov <dmitry.torokhov@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>,
Michael Poole <mdpoole@troilus.org>
Subject: Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev2)
Date: Wed, 19 May 2010 21:03:10 -0400 [thread overview]
Message-ID: <4BF48A4E.4060807@seas.upenn.edu> (raw)
In-Reply-To: <AANLkTik3wNaTCh5JBI7A69QWh9RXvZo0UcuoZ-rQTDlz@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/19/10 20:51, Ping Cheng wrote:
> On Wed, May 19, 2010 at 5:26 PM, Rafi Rubin <rafi@seas.upenn.edu> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 05/19/10 20:13, Ping Cheng wrote:
>>> On Wed, May 19, 2010 at 4:34 PM, Rafi Rubin <rafi@seas.upenn.edu> wrote:
>>>> My understanding is that it would be more like
>>>> + SYN_MT_SLOT 0
>>>> + ABS_MT_POSITION_X x
>>>> + ABS_MT_POSITION_Y y
>>>> + SYN_REPORT
>>>> + SYN_MT_SLOT 0
>>>> + ABS_MT_POSITION_X x
>>>> + ABS_MT_POSITION_Y y
>>>> + SYN_REPORT
>>>> + SYN_MT_SLOT 0
>>>> + ABS_MT_POSITION_X x
>>>> + ABS_MT_POSITION_Y y
>>>> + SYN_MT_SLOT 1
>>>> + ABS_MT_POSITION_X x
>>>> + ABS_MT_POSITION_Y y
>>>> + SYN_REPORT
>>>
>>> You are right if one slot only has or is only allowed to have one
>>> point. My scenario is that one slot can have more than one point.
>>> Basically, my intention is to utilize the MT_SLOT and MT_TRACKING_ID
>>> in such a way that it avoids as much overlap as possible.
>>>
>>> And hopefully it makes sesne in the reality too.
>>
>> Please clarify by what you mean by more than one point.
>
> I might have been confused myself by ABS_MT_BLOB_ID and SYN_MT_SLOT
> here. What I meant by "more than one point" is a contact (or touch, I
> am not sure which one is the right term :) is represented by a few
> (x,y) coordinates. Maybe we should use SYN_MT_SLOT for my case?
>
>> I may be misunderstanding, but I thought that these slots are basically a
>> superior replacement to tracking id.
>>
>> one finger -> one slot
>
> This is what I needed to understand. Is slot for one (x,y) only or can
> it also be used for more than one set of (x,y)?
>
>> But with slots we can use the filtering that input provides, which we've been
>> by-passing with the existing MT protocol (at least that's what I think Henrik's
>> goal is).
>
> Good to know that filtering has already been considered. I know I must
> be out of sync with Henrik's goal. That's why I wanted to show my
> ignorance :).
>
> Ping
>
Hey, sometimes Mark Twain's old advice is good, and sometimes its not.
It's better to keep your mouth shut and be thought a fool than to open it and
leave no doubt. --Mark Twain
I think this is definitely a case where he's wrong. We need to sync up so that
we're all implementing the same protocol, and can move on to the next
interesting problem.
Rafi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkv0ik4ACgkQwuRiAT9o608XmQCdFiTOymC+OEVyQ+atbEdpCiDd
RRYAoIsNpOZpI0Yxr4BG1uEj7Fja2Fyo
=lK01
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-20 1:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 20:10 [PATCH] input: mt: Introduce MT event slots (rev 3) Henrik Rydberg
2010-05-18 20:10 ` [PATCH 2/2] input: mt: Document the MT event slot protocol (rev2) Henrik Rydberg
2010-05-19 2:37 ` Peter Hutterer
2010-05-19 12:12 ` Henrik Rydberg
2010-05-20 0:13 ` Peter Hutterer
2010-05-20 7:11 ` Dmitry Torokhov
2010-05-20 10:46 ` Henrik Rydberg
2010-05-20 10:40 ` Henrik Rydberg
2010-05-24 4:58 ` Peter Hutterer
2010-05-24 6:07 ` Ping Cheng
2010-05-24 10:03 ` Henrik Rydberg
2010-05-24 15:59 ` Dmitry Torokhov
2010-05-24 17:06 ` Ping Cheng
2010-05-24 17:21 ` Dmitry Torokhov
2010-05-24 17:33 ` Ping Cheng
2010-05-24 17:48 ` Henrik Rydberg
2010-05-24 18:04 ` Dmitry Torokhov
2010-05-24 19:19 ` Henrik Rydberg
2010-05-19 22:43 ` Ping Cheng
2010-05-19 23:34 ` Rafi Rubin
2010-05-20 0:13 ` Ping Cheng
2010-05-20 0:26 ` Rafi Rubin
2010-05-20 0:51 ` Ping Cheng
2010-05-20 1:03 ` Rafi Rubin [this message]
2010-05-20 4:18 ` Ping Cheng
2010-05-20 0:21 ` Peter Hutterer
2010-05-20 0:34 ` Rafi Rubin
2010-05-20 7:08 ` Henrik Rydberg
2010-05-20 22:19 ` Ping Cheng
2010-05-20 22:48 ` Henrik Rydberg
2010-05-21 3:35 ` Ping Cheng
2010-05-21 15:19 ` Rafi Rubin
2010-05-21 15:40 ` Ping Cheng
2010-05-21 21:25 ` Henrik Rydberg
2010-05-22 3:10 ` Ping Cheng
2010-05-24 5:25 ` Peter Hutterer
2010-05-24 5:48 ` Ping Cheng
2010-05-24 6:15 ` Peter Hutterer
2010-05-24 9:49 ` 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=4BF48A4E.4060807@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--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=rydberg@euromail.se \
--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).