From: Chase Douglas <chase.douglas@canonical.com>
To: Jussi Pakkanen <jussi.pakkanen@canonical.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: Document the device properties
Date: Mon, 30 Jan 2012 18:05:55 +0100 [thread overview]
Message-ID: <4F26CDF3.5080606@canonical.com> (raw)
In-Reply-To: <4F268BCC.4000008@canonical.com>
On 01/30/2012 01:23 PM, Jussi Pakkanen wrote:
> On 01/30/2012 10:35 AM, Henrik Rydberg wrote:
>> +INPUT_PROP_SEMI_MT:
>> +------------------
>> +Some touchpads, most common between 2008 and 2011, can detect the presence
>> +of multiple contacts without resolving the individual positions; only the
>> +number of contacts and the corresponding bounding box is known. For such
>> +touchpads, the semi-mt property should be set.
>
> A "corresponding bounding box" usually means "a bounding box that
> contains all touches on the touchpad". I've been told (though I have not
> checked it myself) that there are devices that don't do this. They only
> report a bounding box for some subset of touches. If this is the case,
> it should be documented here.
Yeah, I thought Henrik's definition was correct for a long time, but
when Derek Foreman (I think) proposed some patches for the latest
synaptics devices I took a closer look at my semi-mt synaptics trackpad.
The coordinates it gave were locations based on two of the touches. When
three touches are on the touchpad, it gave a bounding box of two of the
touches, and there's no way to tell which two.
-- Chase
next prev parent reply other threads:[~2012-01-30 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 8:35 [PATCH] Input: Document the device properties Henrik Rydberg
2012-01-30 12:23 ` Jussi Pakkanen
2012-01-30 17:05 ` Chase Douglas [this message]
2012-01-31 13:33 ` Daniel Kurtz
2012-01-31 13:33 ` Daniel Kurtz
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=4F26CDF3.5080606@canonical.com \
--to=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jussi.pakkanen@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.