From: Chase Douglas <chasedouglas@gmail.com>
To: Thorsten Wissmann <re06huxa@stud.informatik.uni-erlangen.de>
Cc: "Chris Bagwell" <chris@cnpbagwell.com>,
"Henrik Rydberg" <rydberg@euromail.se>,
linux-input@vger.kernel.org,
"Maximilian Krüger" <maxfragg@gmail.com>,
i4passt@lists.informatik.uni-erlangen.de
Subject: Re: Mixed "pen" and multitouch input devices
Date: Thu, 15 Mar 2012 11:29:37 -0700 [thread overview]
Message-ID: <4F623511.3040907@gmail.com> (raw)
In-Reply-To: <20120315175635.GA23155@stud.informatik.uni-erlangen.de>
On 03/15/2012 10:56 AM, Thorsten Wissmann wrote:
> On Thu, Mar 15, 2012 at 12:27:22PM -0500, Chris Bagwell wrote:
>> Its also true that sharing ABS_X/Y events between both a BTN_TOOL_PEN
>> and a BTN_TOOL_FINGER will confuse most user land apps (they think
>> only touchpads can declare BTN_TOOL_FINGER's but this is a
>> touchscreen) and it also has bad side affects to the kernel's MT
>> pointer emulation functions.
>>
>> You can look at kernel drivers/input/touchscreen/wacom_w8001.c for an
>> example touchscreen that supports pen and at least 2 MT touches on a
>> single /dev/input device (because HW packets come over single serial
>> interface). It does not declare a BTN_TOOL_FINGER nor use pointer
>> emulation to overcome issues I mentioned and xf86-input-wacom
>> understands how to handle this device.
>>
>> If you want to work with other unmodified user land apps (perhaps
>> xf86-input-evdev for touches) then its probably easiest to split pen
>> and touch to separate input devices. drivers/input/tablet/wacom_wac.c
>> shows some examples of that approach but that driver doesn't have to
>> work to hard to split in to 2 input devices because the USB device
>> already puts the events on separate USB interfaces.
>
> OK. We want the device to work with the xf86-input-evdev driver. So we
> will split it into two devices.
Or you could teach evdev to know how to handle mixed devices :). I think
that's the "better" approach over all, but it's up to you.
-- Chase
next prev parent reply other threads:[~2012-03-15 18:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 15:52 Mixed "pen" and multitouch input devices Thorsten Wissmann
2012-03-15 17:27 ` Chris Bagwell
2012-03-15 17:56 ` Thorsten Wissmann
2012-03-15 18:29 ` Chase Douglas [this message]
2012-03-16 1:52 ` Thorsten Wissmann
2012-03-16 2:03 ` Chase Douglas
2012-03-16 2:44 ` Thorsten Wissmann
2012-03-16 2:57 ` Chris Bagwell
2012-03-16 17:33 ` Thorsten Wissmann
2012-03-16 20:27 ` Chase Douglas
2012-03-19 6:39 ` Henrik Rydberg
2012-03-19 15:32 ` Chase Douglas
2012-03-20 1:04 ` Chris Bagwell
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=4F623511.3040907@gmail.com \
--to=chasedouglas@gmail.com \
--cc=chris@cnpbagwell.com \
--cc=i4passt@lists.informatik.uni-erlangen.de \
--cc=linux-input@vger.kernel.org \
--cc=maxfragg@gmail.com \
--cc=re06huxa@stud.informatik.uni-erlangen.de \
--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 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.