From: Trilok Soni <soni.trilok@gmail.com>
To: Ping Cheng <pinglinux@gmail.com>
Cc: Henrik Rydberg <rydberg@enmesh.se>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: input: mt: Software finger tracking in the kernel?
Date: Sun, 21 Mar 2010 00:57:20 +0530 [thread overview]
Message-ID: <5d5443651003201227w27314533w6be3cdd8fb9bf5aa@mail.gmail.com> (raw)
In-Reply-To: <167e8a331003192151o593809bbhcda68e284185dd4a@mail.gmail.com>
Hi Ping,
On Sat, Mar 20, 2010 at 10:21 AM, Ping Cheng <pinglinux@gmail.com> wrote:
> On Fri, Mar 19, 2010 at 3:58 AM, Henrik Rydberg <rydberg@enmesh.se> wrote:
>> Hi Dmitry,
>>
>> there is an ongoing discussion about adding multitouch to X
>> (http://lists.x.org/archives/xorg-devel/2010-March/006206.html), which is
>> beginning to take on more solid form.
>>
>> One of the suggestions emerging from that discussion is to add the software
>> finger tracking to the kernel. Back in summer 2009 when I thought about this, I
>> disregarded it as being too experimental. I have since then reconsidered,
>> starting to think it really is the right place.
>>
>> The MT protocol allows applications to take advantage of multi-contact hardware,
>> but leaves the problems of finger tracking and filtering to the user. Arguably,
>> no application can make good use of MT without these, so the problem is pushed
>> forward, in this case to evdev or equivalent.
>>
>> The knowledge of signal-to-noise ratios and prior input states resides in the
>> kernel. Because of this, the finger matching and filtering would naturally
>> reside within the kernel.
>>
>> So, if there were to appear patches to include matching in the input core, would
>> you consider them? :-)
>
> I support the idea to add a tracking ID and a filter to _MT_. I'd
> also like to make the filtering method more "device driver developer"
> friendly, i.e., give the developer the option to turn the filter on or
> off. If you plan to use a constant for the filtering method, please
> allow the developer to choose that constant too.
>
> Another attribute associated with _MT_ is the pressure/capacity.
> Report this value would offer more room for MT-aware application to
> add new features.
We have ABS_MT_PRESSURE added recently. I hope you are asking the same.
--
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni
--
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-03-20 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 10:58 input: mt: Software finger tracking in the kernel? Henrik Rydberg
2010-03-19 11:38 ` Trilok Soni
2010-03-20 4:51 ` Ping Cheng
2010-03-20 19:27 ` Trilok Soni [this message]
2010-03-20 19:32 ` Ping Cheng
2010-03-20 19:44 ` Dmitry Torokhov
2010-03-20 21:59 ` Henrik Rydberg
2010-03-20 22:31 ` Henrik Rydberg
2010-03-21 3:06 ` Rafi Rubin
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=5d5443651003201227w27314533w6be3cdd8fb9bf5aa@mail.gmail.com \
--to=soni.trilok@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pinglinux@gmail.com \
--cc=rydberg@enmesh.se \
/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).