From: Chase Douglas <chase.douglas@canonical.com>
To: Ping Cheng <pinglinux@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: New multitouch touchscreen over serial support
Date: Wed, 26 May 2010 20:10:12 -0400 [thread overview]
Message-ID: <1274919012.317.57.camel@mini> (raw)
In-Reply-To: <AANLkTilRYhWUlR57ZdVIb0wH-8zKwNDXnUQAu1vFLGpz@mail.gmail.com>
On Wed, 2010-05-26 at 15:52 -0700, Ping Cheng wrote:
> On Wed, May 26, 2010 at 3:29 PM, Chase Douglas
> <chase.douglas@canonical.com> wrote:
> > IMHO, the best support for this driver would be as a
> > kernel module that could use the input subsystem to send multitouch
> > events up through the evdev interface.
>
> Sure, you can add yours and a bunch of the other serial WACfxxx
> devices into the kernel under input/touchscreen (I believe Jaya Kumar
> <jayakumar.lkml@gmail.com> has added the pen-only one there already).
> But you would need to update the Wacom X driver as well. Without the
> proper X driver to work with it, kernel driver is pretty much useless.
> Or you may be able to let X evdev driver take care of it as a generic
> touch screen device. I don't know how good the X evdev driver handles
> the touch events though.
This is actually why I think it should be in the kernel instead of in X.
The kernel has an interface for multitouch events through evdev. It's
standardized, and the X multitouch support will be predicated on it. So
if we want any multitouch support for these devices in linux, it will
have to go through the kernel input subsystem one way or another.
Also, an evdev based driver shouldn't require any new X support.
(I'm new to linux input stuff, if anyone feels I've mischaracterized
multitouch support in linux, please speak up :)
> > Do you have any information on this device?
>
> What kind of information do you need? I have the protocol and you can
> get one if you sign an NDA with Wacom.
>
> > Would it be possible to write a driver?
>
> Anything is possible on Linux :). Someone has to do the work though.
> I do not have time to work on it. That is the reality.
Sure. I am personally interested in writing the driver. I need to do
some work on my end before I can commit to anything, but I will get back
to you with more details.
Thanks,
-- Chase
prev parent reply other threads:[~2010-05-27 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 22:29 New multitouch touchscreen over serial support Chase Douglas
2010-05-26 22:52 ` Ping Cheng
2010-05-27 0:10 ` Chase Douglas [this message]
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=1274919012.317.57.camel@mini \
--to=chase.douglas@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=pinglinux@gmail.com \
/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).