From: Chase Douglas <chase.douglas@canonical.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Rafi Rubin <rafi@seas.upenn.edu>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Ping Cheng <pinglinux@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Mika Kuoppala <mika.kuoppala@nokia.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
Benjamin Tissoires <tissoire@cena.fr>,
Stephane Chatty <chatty@enac.fr>,
Michael Poole <mdpoole@troilus.org>
Subject: Re: [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3)
Date: Sat, 22 May 2010 10:46:22 -0400 [thread overview]
Message-ID: <1274539582.13705.132.camel@cndougla-ubuntu> (raw)
In-Reply-To: <4BF7B438.8000001@euromail.se>
On Sat, 2010-05-22 at 12:38 +0200, Henrik Rydberg wrote:
> Getting serious, it is anyone's guess what will happen next, but I was picturing
> a table, with a large multitouch screen and buttons along the side of the table.
> Sure, we can do "ABS_BTN_0", "ABS_BTN_1", etc, but with slots in place, it seems
> more natural to use something like "ABS_MT_BTN_X". While at it, REL_MT event
> makes sense for those touchscreen techniques which register changes, like
> acoustic pulse recognition.
Shouldn't this be handled in userspace? I don't think we want to be
quirking drivers for instances where the same touchscreen is overlaid on
buttons in some cases, but not in others. If we don't quirk, we'd need
some mechanism to tell the driver about such buttons.
-- Chase
next prev parent reply other threads:[~2010-05-22 14:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 15:55 [PATCH 1/2] input: mt: Introduce MT event slots (rev 4) Henrik Rydberg
2010-05-21 15:55 ` [PATCH 2/2] input: mt: Document the MT event slot protocol (rev3) Henrik Rydberg
2010-05-21 16:30 ` Ping Cheng
2010-05-21 16:36 ` Henrik Rydberg
2010-05-21 16:52 ` Dmitry Torokhov
2010-05-21 16:56 ` Henrik Rydberg
2010-05-21 17:22 ` Dmitry Torokhov
2010-05-21 17:29 ` Henrik Rydberg
2010-05-21 17:41 ` Dmitry Torokhov
2010-05-21 17:49 ` Henrik Rydberg
2010-05-22 3:52 ` Ping Cheng
2010-05-22 7:08 ` Henrik Rydberg
2010-05-22 9:11 ` Henrik Rydberg
2010-05-22 9:33 ` Rafi Rubin
2010-05-22 10:38 ` Henrik Rydberg
2010-05-22 14:46 ` Chase Douglas [this message]
2010-05-22 17:47 ` Henrik Rydberg
2010-05-22 20:52 ` Chase Douglas
2010-05-22 20:56 ` Dmitry Torokhov
2010-05-22 21:09 ` Henrik Rydberg
2010-05-22 20:16 ` Dmitry Torokhov
2010-05-22 21:15 ` Henrik Rydberg
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=1274539582.13705.132.camel@cndougla-ubuntu \
--to=chase.douglas@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdpoole@troilus.org \
--cc=mika.kuoppala@nokia.com \
--cc=peter.hutterer@who-t.net \
--cc=pinglinux@gmail.com \
--cc=rafi@seas.upenn.edu \
--cc=rydberg@euromail.se \
--cc=tissoire@cena.fr \
/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).