From: Michael Poole <mdpoole@troilus.org>
To: Florian Echtler <floe@butterbrot.org>
Cc: linux-input@vger.kernel.org
Subject: Re: Preferred way for a multitouch driver?
Date: Sun, 11 Apr 2010 12:54:40 -0400 [thread overview]
Message-ID: <87633yhqun.fsf@troilus.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1004111828030.29274@butterbrot.org> (Florian Echtler's message of "Sun, 11 Apr 2010 18:41:04 +0200 (CEST)")
Florian Echtler writes:
> Hello everyone,
>
> I've just bought a Lenovo S10-3t convertible netbook, and now I'm
> experimenting with the "multitouch" screen (dual-touch, rather). It's
> being recognized as a HID device, and using hid-device-dump, I can
> nicely read the reports of both fingers. There's also some hacks
> floating around which use xf86-input-hidtouch, but AFAICT that doesn't
> do any kind of multitouch.
>
> From lurking here on the list, I've gathered that the evdev interface
> by now fully supports all kinds of multitouch events, so I guess the
> preferred way would be a hiddev-to-evdev bridge of some kind, right?
You don't need that -- HID drivers already generate evdev events.
> Can somebody point me into the right direction, e.g. to some other
> driver which also works that way?
You can find them by grepping for ABS_MT_ in the drivers/hid/ directory.
hid-3m-pct, hid-magicmouse, hid-mosart, hid-ntrig, hid-quanta and
hid-stratum all generate multitouch events. Most of them use standard
HID report descriptors; however, hid-magicmouse has to translate input
reports that don't have published descriptors. Depending on how the
screen behaves, you'll probably want to look more at the other drivers
than hid-magicmouse.
Michael Poole
next prev parent reply other threads:[~2010-04-11 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 16:41 Preferred way for a multitouch driver? Florian Echtler
2010-04-11 16:54 ` Michael Poole [this message]
2010-04-11 19:02 ` Rafi Rubin
2010-04-11 20:09 ` Florian Echtler
2010-04-11 20:51 ` Stéphane Chatty
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=87633yhqun.fsf@troilus.org \
--to=mdpoole@troilus.org \
--cc=floe@butterbrot.org \
--cc=linux-input@vger.kernel.org \
/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).