All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Florian Ragwitz" <rafl@debian.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"Stéphane Chatty" <chatty@enac.fr>,
	"Benjamin Tissoires" <tissoire@cena.fr>
Subject: Re: [PATCH 2/2] elantech: Report multitouch with proper ABS_MT messages
Date: Thu, 06 May 2010 00:15:26 +0200	[thread overview]
Message-ID: <4BE1EDFE.20001@euromail.se> (raw)
In-Reply-To: <4BE1E0CF.9020008@tudelft.nl>

Éric Piel wrote:
> Op 05-05-10 21:06, Henrik Rydberg schreef:
>> Éric Piel wrote:
>>> 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.
>> Something like fingermgmt in OSX? Not to my knowledge. The touchd project
>> includes some graphics via python, but is not based on MT events. Maybe our
>> friends at ENAC has something cooking?
> 
> Thanks a lot for the tips.
> I've hacked up an app which does just this, based on touchd and
> pyinputevent.

Thanks for the app, works nicely after adjusting the touchpad resolution to fit
my bcm5974.

Henrik

> Apparently when there are two fingers, the hardware doesn't report
> really the finger coordinates but the lowest and highest points of the
> rectangle defined by the two fingers.

I take it you are referring to the enumeration of the fingers, the order in
which they appear on the wire?

Henrik
--
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 22:15 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
2010-05-05 19:06           ` Henrik Rydberg
2010-05-05 21:19             ` Éric Piel
2010-05-05 22:15               ` Henrik Rydberg [this message]
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=4BE1EDFE.20001@euromail.se \
    --to=rydberg@euromail.se \
    --cc=E.A.B.Piel@tudelft.nl \
    --cc=chatty@enac.fr \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=rafl@debian.org \
    --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 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.