From: Greg KH <greg@kroah.com>
To: Matt Helsley <matt.helsley@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix genius pensketch 12x9 tablet
Date: Sat, 13 Dec 2008 00:55:56 -0800 [thread overview]
Message-ID: <20081213085556.GB12194@kroah.com> (raw)
In-Reply-To: <1229155530.13862.9.camel@molly>
On Sat, Dec 13, 2008 at 12:05:30AM -0800, Matt Helsley wrote:
> On Fri, 2008-12-12 at 23:53 -0800, Greg KH wrote:
> > On Fri, Dec 12, 2008 at 10:42:28PM -0800, Matt Helsley wrote:
> > > The Genius PenSketch 12x9 tablet has a puck (labeled a
> > > "Tablet Mouse") in addition to a pen. Without registering a quirk
> > > the tablet appears to be a single input device that reports the
> > > wrong axis information in /proc/bus/input/devices, and sends
> > > incorrect events (e.g. ABS_Z instead of ABS_Y). This information
> > > confuses the X evdev driver and makes the device impossible to
> > > use.
> > >
> > > The quirk fixes events and splits the device into multiple input
> > > event devices so that at least the puck is useful.
> > >
> > > Signed-off-by: Matt Helsley <matt.helsley@gmail.com>
> > > ---
> > > NOTE: xinput lists the puck but not the pen. I've been using a
> > > python script to verify the contents of the events independently
> > > of X and, as far as I can tell, the remaining problems are in X
> > > itself.
> >
> > I have a tablet here that I'm having troubles getting to work. Any
> > chance I could get a copy of your python script so I can try to debug
> > what is going wrong, and if it's a X problem or a kernel issue like you
> > found for your device?
> >
> > thanks,
> >
> > greg k-h
>
> Sure. Sometime around 2.6.24 I updated this script (originally by Micah
> Dowty) to include more evdev #defines, work on 64-bit systems, and
> decode some bitvectors into their C symbols.
Thanks, it has helped out, although it doesn't seem to "poll" the device
properly for some reason to get any events from the device. I wonder if
X is grabbing it before this script has a chance to, I'll play around
with that next...
greg k-h
next prev parent reply other threads:[~2008-12-13 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 6:42 [PATCH] Fix genius pensketch 12x9 tablet Matt Helsley
2008-12-13 7:53 ` Greg KH
[not found] ` <20081213075342.GA11346-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2008-12-13 8:05 ` Matt Helsley
2008-12-13 8:55 ` Greg KH [this message]
[not found] ` <20081213085556.GB12194-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2008-12-13 9:51 ` Matt Helsley
2008-12-13 13:30 ` Jiri Kosina
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=20081213085556.GB12194@kroah.com \
--to=greg@kroah.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matt.helsley@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