From: Chase Douglas <chase.douglas@canonical.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Yufeng Shen <miletus@chromium.org>,
linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, Daniel Kurtz <djkurtz@chromium.org>,
Andrew de los Reyes <adlr@chromium.org>
Subject: Re: [PATCH] HID: magicmouse: Implement Multi-touch Protocol B (MT-B)
Date: Mon, 02 Jul 2012 11:50:52 -0700 [thread overview]
Message-ID: <4FF1ED8C.2080805@canonical.com> (raw)
In-Reply-To: <20120702100741.GA1496@polaris.bitmath.org>
On 07/02/2012 03:07 AM, Henrik Rydberg wrote:
> On Thu, Jun 28, 2012 at 03:54:31PM -0400, Yufeng Shen wrote:
>> The driver for Apple Magic Trackpad/Mouse currently uses
>> Multi-touch Protocol A (MT-A) to report touch events and uses
>> ABS_MT_TRACKING_ID to do finger tracking. The fact of the device
>> being able to track individual finger makes it possible to
>> report touch events using MT-B. This patch adds the support
>> for the driver to report MT-B and makes it configurable through
>> module parameter so that existing codes that are relying on its
>> MT-A implemtation don't get affected.
>
> Are there any such codes? Most systems, if not all, seem to use mtdev,
> which can handle both protocols. I do not think a parameter switch is
> a good idea. Switching to MT-B or leaving things as is look like the
> viable options.
Yes, let's just switch to MT-B :). Part of open source is that one can
look at other implementations to figure out how to make your own new
device work. We don't want to proliferate MT-A since MT-B is the way
forward.
In fact, I would also suggest preceding this patch with one that removes
the switch to turn touch reporting on and off. It's really unnecessary.
I bet no one in the world turns it off :).
-- Chase
next prev parent reply other threads:[~2012-07-02 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 19:54 [PATCH] HID: magicmouse: Implement Multi-touch Protocol B (MT-B) Yufeng Shen
2012-07-02 10:07 ` Henrik Rydberg
2012-07-02 18:50 ` Chase Douglas [this message]
2012-07-02 18:52 ` Chase Douglas
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=4FF1ED8C.2080805@canonical.com \
--to=chase.douglas@canonical.com \
--cc=adlr@chromium.org \
--cc=djkurtz@chromium.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miletus@chromium.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 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).