linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Éric Piel" <E.A.B.Piel@tudelft.nl>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Florian Ragwitz <rafl@debian.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH 2/2] elantech: Report multitouch with proper ABS_MT messages
Date: Wed, 05 May 2010 20:35:03 +0200	[thread overview]
Message-ID: <4BE1BA57.5080709@tudelft.nl> (raw)
In-Reply-To: <4BE1B84C.1040903@euromail.se>

Op 05-05-10 20:26, Henrik Rydberg schreef:
> Éric Piel wrote:
:
>> Let me give you some more details. From what is seems, the hardware can
>> reports the width of a touch, but only when there is one single touch.
>> So far we report it via ABS_TOOL_WIDTH. When there is 2 or 3 touches,
>> the width is unknown. So the precise question is:
>> Should we report also ABS_MT_TOUCH_MAJOR in addition to ABS_TOOL_WIDTH,
>> whenever it is known (ie: one finger), or just not bother and only
>> report ABS_TOOL_WIDTH?
> 
> With only partial information available it will not be of much use anyway, so
> omitting ABS_MT_TOUCH is probably best. The ABS_TOOL_WIDTH will most likely not
> be used by a driver either (it wont in the Multitouch X Driver anyways). The
> synaptics driver cares for palm detection, but the scale has to be very specific
> to work properly (i.e., requires testing with synaptics to be useful).
Thanks for clarifying!

BTW, does anyone know a graphical app which reads the MT events from a
/dev/input/eventX device and displays them as points in a window? That
would be rather helpful to reverse-engineer/debug multitouch hardwares.

Eric

--
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

  reply	other threads:[~2010-05-05 18:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 12:20 [PATCH 2/2] elantech: Report multitouch with proper ABS_MT messages Éric Piel
2010-05-05 16:38 ` Dmitry Torokhov
2010-05-05 17:06   ` Éric Piel
2010-05-05 17:15     ` Dmitry Torokhov
2010-05-05 17:36       ` Éric Piel
2010-05-05 18:03     ` Henrik Rydberg
2010-05-05 18:05     ` Florian Ragwitz
2010-05-05 18:11       ` Henrik Rydberg
2010-05-05 18:25         ` Dmitry Torokhov
2010-05-05 18:29           ` Henrik Rydberg
2010-05-05 20:51             ` Dmitry Torokhov
2010-05-05 18:01   ` Henrik Rydberg
2010-05-05 18:14     ` Éric Piel
2010-05-05 18:26       ` Henrik Rydberg
2010-05-05 18:35         ` Éric Piel [this message]
2010-05-05 19:06           ` Henrik Rydberg
2010-05-05 21:19             ` Éric Piel
2010-05-05 22:15               ` Henrik Rydberg
2010-05-05 22:53                 ` Éric Piel
2010-05-06  8:49             ` Stéphane Chatty
2010-05-06  9:26               ` Mohamed Ikbel Boulabiar
     [not found]               ` <g2t45cc95261005060217nfbde1177j1dc97028a3b53c3c@mail.gmail.com>
2010-05-06 11:40                 ` Henrik Rydberg
2010-05-06  9:22             ` Hennerich, Michael
2010-05-06 11:38               ` Henrik Rydberg
2010-05-05 23:00           ` Éric Piel

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=4BE1BA57.5080709@tudelft.nl \
    --to=e.a.b.piel@tudelft.nl \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=rafl@debian.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).