Re: [Linuxwacom-discuss] Bamboo Pad 0x318

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

On 06/01/14 17:09, Chris Bagwell wrote:
> On Mon, Jan 6, 2014 at 4:17 AM, Chris Wallace
> <chr...@ci...> wrote:
>>
>> You're correct, removing the .type enabled some further information to be
>> appended. Using BAMBOO_PT, I get
>>
>> $sudo evtest
>> /dev/input/event5: Wacom Bamboo Pad, USB 318 Pen
>> /dev/input/event6: Wacom Bamboo Pad, USB 318 Pen
>> /dev/input/event7: Wacom Bamboo Pad, USB 318 Finger
>> $ xsetwacom --list devices
>> Wacom Bamboo Pad, USB 318 Pen stylus id: 12 type: STYLUS
>> Wacom Bamboo Pad, USB 318 Pen eraser id: 13 type: ERASER
>> Wacom Bamboo Pad, USB 318 Pen stylus id: 14 type: STYLUS
>> Wacom Bamboo Pad, USB 318 Pen eraser id: 15 type: ERASER
>> Wacom Bamboo Pad, USB 318 Finger touch id: 16 type: TOUCH
>> Wacom Bamboo Pad, USB 318 Finger pad id: 17 type: PAD
> That surprises me that BAMBOO_PT correctly detected touch interface
> but lets go with it for now.  That second Pen is really the fake
> keyboard interface which I think we can ignore for now and see if we
> can get touch working.
>
>> and using INTUOSHT, I get
>>
>> $ sudo evtest
>> /dev/input/event5: Wacom Bamboo Pad, USB 318 Finger
>> /dev/input/event6: Wacom Bamboo Pad, USB 318 Finger
>> /dev/input/event7: Wacom Bamboo Pad, USB 318 Finger
>> $ xsetwacom --list devices
>> Wacom Bamboo Pad, USB 318 Finger touch id: 12 type: TOUCH
>> Wacom Bamboo Pad, USB 318 Finger pad id: 13 type: PAD
>> Wacom Bamboo Pad, USB 318 Finger touch id: 14 type: TOUCH
>> Wacom Bamboo Pad, USB 318 Finger pad id: 15 type: PAD
>> Wacom Bamboo Pad, USB 318 Finger touch id: 16 type: TOUCH
>> Wacom Bamboo Pad, USB 318 Finger pad id: 17 type: PAD
>>
>> Neither seems quite right, in that neither produces a responsive Bamboo!
> Does the pen work with BAMBOO_PT?  I don't expect it to work for
> INTUOSHT since no are labeled as Pen.

Nothing works with either - neither pen, nor touch.

>
>
>  From here, I'd try to see if packets are actually making it to driver.
>   You can put a printk at top of wacom_bpt_irq() to see if occurring.
> I'd specifically print out the value of len and wacom->data[0] and see
> if that tells you why packets are being discarded (if they are making
> it to driver that is).
Thank you for your continuing help.  I don't think wacom_bpt_irq() is 
ever called.  From dropping a few printk around, I think everything 
stops at wacom_sys_irq() when urb->status is non-zero, but not an 
expected non-zero value.  I put the following in wacom_sys_irq:

> --- a/3.7/wacom_sys.c
> +++ b/3.7/wacom_sys.c
> @@ -103,6 +103,9 @@ static void wacom_sys_irq(struct urb *urb)
>          struct device *dev = &wacom->intf->dev;
>          int retval;
>   
> +       printk("!!! This is wacom_sys_irq\n");
> +       printk("urb->status %d\n", urb->status);
> +       printk("urb->actual_length %d\n", urb->actual_length);
>          switch (urb->status) {
>          case 0:
>                  /* success */

Which gave the following with dmesg:

[341928.113381] input: Wacom Bamboo Pad, USB 318 Pen as 
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.0/input/input57
[341928.114109] input: Wacom Bamboo Pad, USB 318 Pen as 
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.1/input/input58
[341928.114754] input: Wacom Bamboo Pad, USB 318 Finger as 
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7:1.2/input/input59
[341928.114880] usbcore: registered new interface driver wacom
[341928.148841] !!! This is wacom_sys_irq
[341928.148847] urb->status -2
[341928.148848] urb->actual_length 0
[341928.167785] !!! This is wacom_sys_irq
[341928.167789] urb->status -2
[341928.167791] urb->actual_length 0
[341928.212615] !!! This is wacom_sys_irq
[341928.212619] urb->status -2
[341928.212621] urb->actual_length 0
[341928.796776] !!! This is wacom_sys_irq
[341928.796782] urb->status -75
[341928.796784] urb->actual_length 0
[341929.171666] !!! This is wacom_sys_irq
[341929.171670] urb->status -75
[341929.171670] urb->actual_length 0

> This page may help you understand USB protocol a little better. You
> Pen/Stylus packets should look like that page describes but your touch
> packets will not be described (only the older Bamboo Touch v1 or v2
> are described).
>
> http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=USB_Protocol
>
> Your touch packet will either be a new format that driver doesn't
> understand, a pre-existing format which could be called Bamboo Touch
> v3, or a modified version of v3.  You'll see references to bpt3 in
> wacom_wac.c that refer to this Bamboo Touch v3 format used by most of
> the latest tablets with touch... minus your new Bamboo Pad which I do
> not know what format it uses.
So monitoring the usb gives output below.  Is this familiar/expected?

$ lsusb | grep Wacom
Bus 002 Device 004: ID 056a:0318 Wacom Co., Ltd
$ sudo cat /sys/kernel/debug/usb/usbmon/2u |grep 2:004
ffff8804143da600 2800438721 C Ii:2:004:1 -75:2 0
ffff8804143da600 2800438729 S Ii:2:004:1 -115:2 10 <
ffff8804143da600 2802430756 C Ii:2:004:1 -75:2 0
ffff8804143da600 2802430758 S Ii:2:004:1 -115:2 10 <
ffff8804143da600 2804426783 C Ii:2:004:1 -75:2 0
ffff8804143da600 2804426791 S Ii:2:004:1 -115:2 10 <
ffff8804143da600 2805994806 C Ii:2:004:1 -75:2 0      ## <- start using 
stylus here
ffff8804143da600 2805994814 S Ii:2:004:1 -115:2 10 <
ffff8804143da600 2806004802 C Ii:2:004:1 -75:2 0
ffff8804143da600 2806004807 S Ii:2:004:1 -115:2 10 <
ffff8804143da600 2806014651 C Ii:2:004:1 -75:2 0
ffff8804143da600 2806014652 S Ii:2:004:1 -115:2 10 <
ffff8804143da600 2806026750 C Ii:2:004:1 -75:2 0
ffff8804143da600 2806026753 S Ii:2:004:1 -115:2 10 <

Apologies for all the questions - I really am beyond my comfort zone here.

Thank you for your help,

Chris