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:

quoted

On Fri, Dec 12, 2008 at 10:42:28PM -0800, Matt Helsley wrote:

quoted

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 <redacted>
---
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