From: Henrik Rydberg <rydberg@euromail.se>
To: "Stéphane Chatty" <chatty@enac.fr>
Cc: Rudy Huang <rudy_huang@sitronix.com.tw>,
Alan Cox <alan@linux.intel.com>,
linux-input@vger.kernel.org, jkosina@suse.cz
Subject: Re: Sitronix ST9RM01 multitouch panel
Date: Tue, 28 Sep 2010 21:43:22 +0200 [thread overview]
Message-ID: <4CA2455A.9070109@euromail.se> (raw)
In-Reply-To: <296EC52A-446B-4BE2-B5D6-567B83C7DDBC@enac.fr>
On 09/28/2010 09:37 PM, Stéphane Chatty wrote:
>
> Le 28 sept. 10 à 21:10, Henrik Rydberg a écrit :
>
>> On 09/28/2010 08:49 PM, Stéphane Chatty wrote:
>> [...]
>>>
>>
>>>> This usage of ABS_MT_TRACKING_ID is not ideal. The HID contact id normally maps
>>>> to a slot number, which suggests the MT slots protocol be used instead.
>>>
>>> I'm working on a slot-based version of the Stantum driver, and have had a look
>>> into this. The Stantum firmware actually cycles over 8-bit values for its
>>> ContactID. In this, it conforms more to the definition you gave for
>>> ABS_MT_TRACKING_ID ("The slot protocol requires the use of the
>>> ABS_MT_TRACKING_ID, either provided by the hardware or computed from the raw
>>> data [5]") than to a slot number, doesn't it? Nevertheless, given our recent
>>> exchanges about the 3M driver, I planned to use the driver's own tracking ID.
>>>
>>> Your thoughts?
>>
>>
>> Excellent. :-) Speaking of drivers and multiplication, I think many of the
>> current drivers could in fact be merged. It seems we have two or three different
>> types so far, and different manufacturers may well be served by the same driver.
>
> Yes, I have started reviewing all devices and making a summary of their
> differences in that very purpose. Among the things we'll need is some standard
> way for calling the filtering function at the end of a set of fingers.
> CONTACTCOUNT is a good candidate, but I need to check some devices. One thing
> bothers me though. It is that hid-core has the whole information, then is splits
> it and calls us repeatedly, then we more or less undo that by storing the
> information and trying to determine the last time it calls us.
Right. A hid-mt device based on the raw protocol could be a good idea - after we
reduced the current set a bit. :-)
Cheers,
Henrik
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-28 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 9:40 [PATCH] Sitronix ST9RM01 multitouch panel Alan Cox
2010-09-28 17:50 ` Stéphane Chatty
2010-09-29 7:31 ` Gowri Ries - Stantum
2010-09-28 18:24 ` Henrik Rydberg
2010-09-28 18:49 ` Stéphane Chatty
2010-09-28 19:10 ` Henrik Rydberg
2010-09-28 19:37 ` Stéphane Chatty
2010-09-28 19:43 ` Henrik Rydberg [this message]
2010-09-29 13:12 ` Jiri Kosina
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=4CA2455A.9070109@euromail.se \
--to=rydberg@euromail.se \
--cc=alan@linux.intel.com \
--cc=chatty@enac.fr \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=rudy_huang@sitronix.com.tw \
/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).