On Sun, Feb 19, 2012 at 2:33 AM, Adam Nielsen <a.niel...@shikadi.net> wrote:
>
> So far everything works fine in evdev, but I am still having problems
> getting the X driver to pick up the device.
>
> Currently the interface with the buttons works (the L and R buttons on the
> tablet work as left and right mouse buttons) however the stylus interface is
> still being ignored.
>
> I got the logging working with 'xinput set-prop device_name "Wacom Debug
> Levels" 10 10' from your other e-mail and the correct events are logged:
>
> [ 26093.031] (II) Wacom DTI520UB/L stylus (10:wcmReady): 1 numbers of data
> [ 26093.031] (II) /dev/input/event13 (10:wcmReadPacket): fd=75
> [ 26093.031] (II) /dev/input/event13 (1:wcmReadPacket): pos=0 remaining=256
> [ 26093.031] (II) /dev/input/event13 (10:wcmReadPacket): buffer has 72 bytes
> [ 26093.031] (II) /dev/input/event13 (10:usbParseEvent):
> [ 26093.031] (II) /dev/input/event13 (10:usbParseEvent):
> [ 26093.031] (II) /dev/input/event13 (10:usbParseEvent):
> [ 26093.031] (II) /dev/input/event13 (6:usbDispatchEvents): 3 events
> received
> [ 26093.031] (II) /dev/input/event13 (10:wcmEvent): channel = 0
> [ 26093.031] (II) /dev/input/event13 (10:wcmEvent): c=0 i=0 t=0 s=1 x=3806
> y=2352 b=0 p=0 rz=0 tx=0 ty=0 aw=0 aw2=0 rw=0 t=0 px=0 st=0 cs=0
> [ 26093.031] (II) Wacom DTI520UB/L stylus (10:wcmReady): 0 numbers of data
> [ 26093.031] (II) Wacom DTI520UB/L stylus (10:wcmDevReadInput): Read (1)
>
> Yet "xinput test" doesn't display any events for the stylus interface. Any
> ideas what I could be doing wrong?
Only seeing this small sample, Its probably the proximity value thats
not working. When px=0, the driver will not post X/Y events to X
server.
Also, the device type is set to 0 ("t=0"). Events are discarded when
no device_type is set.
What version of xf86-input-wacom are you running? You may need to
upgrade for it to work with whats sometimes called "generic" tablets.
I think you need at least version 0.11 for that support.
Or you can modify your kernel side code a little to not be "generic".
>
> I am configuring the device like this in wacom_setup_input_capabilities():
>
> case WACOM_DTI:
> __clear_bit(ABS_MISC, input_dev->absbit);
> switch (features->device_type) {
> case BTN_TOOL_PEN:
> __set_bit(BTN_TOOL_PEN, input_dev->keybit);
> __set_bit(BTN_STYLUS, input_dev->keybit);
> __set_bit(BTN_STYLUS2, input_dev->keybit);
>
> __set_bit(INPUT_PROP_DIRECT, input_dev->propbit);
> break;
That all looks good. The ABS_MISC that your turning off is what
xf86-input-wacom used to key off of to set device_type on its side.
You can delete that line and then start sending it; using
wacom_dtu_irq() as a guide on how to do that.
But it also shouldn't be needed in newer X input drivers.
Chris
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
