From: Chase Douglas <chase.douglas@canonical.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>, Ping Cheng <pingc@wacom.com>,
Chris Bagwell <chris@cnpbagwell.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] input: mt: Move tracking and pointer emulation to input-mt (rev2)
Date: Mon, 06 Dec 2010 10:40:21 -0800 [thread overview]
Message-ID: <4CFD2E15.50105@canonical.com> (raw)
In-Reply-To: <1291224069-11770-1-git-send-email-rydberg@euromail.se>
On 12/01/2010 09:21 AM, Henrik Rydberg wrote:
> The drivers using the type B protocol all report tracking information
> the same way. The contact id is semantically equivalent to
> ABS_MT_SLOT, and the handling of ABS_MT_TRACKING_ID only complicates
> the driver. The situation can be improved upon by providing a common
> pointer emulation code, thereby removing the need for the tracking id
> in the driver. This patch moves all tracking event handling over to
> the input core, simplifying both the existing drivers and the ones
> currently in preparation.
When two or more fingers are down, one of the fingers controls
ABS_{X,Y}. I think the aim is to emulate current behavior for
synaptics-style touchpads, which average the position in firmware. Thus,
we should be averaging the touch positions to generate the ABS_{X,Y} values.
-- Chase
next prev parent reply other threads:[~2010-12-06 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 17:21 [PATCH 3/3] input: mt: Move tracking and pointer emulation to input-mt (rev2) Henrik Rydberg
2010-12-02 1:25 ` Ping Cheng
2010-12-06 18:40 ` Chase Douglas [this message]
2010-12-06 19:52 ` Chris Bagwell
2010-12-06 20:00 ` Chase Douglas
2010-12-06 22:56 ` Chris Bagwell
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=4CFD2E15.50105@canonical.com \
--to=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=pingc@wacom.com \
--cc=rydberg@euromail.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).