« Return to Thread: Getting USB TabletPCs supported (f.ex. Asus R1F)
Fwd: Getting USB TabletPCs supported (f.ex. Asus R1F)
by Andrew Zappacky
::
Rate this Message:
I accidentally didn't click "Reply to all", i apologize
---------- Forwarded message ----------
From: Andrew Zappacky <zappacky@...>
Date: Feb 9, 2008 7:53 PM
Subject: Re: [Linuxwacom-devel] Getting USB TabletPCs supported (f.ex. Asus R1F)
To: Magnus Vigerlöf <Magnus.Vigerlof@...>
I've tried everything and I simply can not get the tablet to talk to me.
I opened up windows xp in KVM and usb-sniffed it until the tablet
started talking (oddly, the tablet didn't work in the vm). I then
edited the wacom driver to send the same sequence of packets, no
matter what combination of packets i sent, the tablet came back with
error -32 and didn't talk. I don't know how I should modify these
packets, I am pasting the output from the usbmonitor from the VM so
perhaps somebody could give me a hand.
f6db0340 2106737586 S Ci:007:00 s 80 08 0000 0000 0001 1 <
f6db0340 2106737763 C Ci:007:00 0 1 = 01
f6db0340 2106737774 S Ci:007:00 s 81 0a 0000 0000 0001 1 <
f6db0340 2106737885 C Ci:007:00 0 1 = 00
f6a98640 2116336662 S Ci:007:00 s 80 06 0100 0000 0040 64 <
f6a98640 2116336977 C Ci:007:00 0 18 = 12010101 00000008 6a059400 01000000 0001
f6a98640 2116436650 S Ci:007:00 s 80 06 0100 0000 0012 18 <
f6a98640 2116436970 C Ci:007:00 0 18 = 12010101 00000008 6a059400 01000000 0001
f6a98640 2116456650 S Ci:007:00 s 80 06 0200 0000 0009 9 <
f6a98640 2116456966 C Ci:007:00 0 9 = 09022900 010100c0 00
f6a98640 2116473383 S Ci:007:00 s 80 06 0200 0000 00ff 255 <
f6a98640 2116473966 C Ci:007:00 0 41 = 09022900 010100c0 00090400
00020300 00000921 10010001 221a0007 05810308
f6a98640 2116506682 S Ci:007:00 s 80 06 0100 0000 0012 18 <
f6a98640 2116507089 C Ci:007:00 0 18 = 12010101 00000008 6a059400 01000000 0001
f6a98640 2116526643 S Ci:007:00 s 80 06 0200 0000 0009 9 <
f6a98640 2116526961 C Ci:007:00 0 9 = 09022900 010100c0 00
f6a98640 2116543364 S Ci:007:00 s 80 06 0200 0000 0029 41 <
f6a98640 2116543961 C Ci:007:00 0 41 = 09022900 010100c0 00090400
00020300 00000921 10010001 221a0007 05810308
f6a98640 2116576637 S Co:007:00 s 00 09 0001 0000 0000 0
f6a98640 2116576833 C Co:007:00 0 0
f6a98640 2116619966 S Co:007:00 s 21 0a 0000 0000 0000 0
f6a98640 2116620081 C Co:007:00 0 0
f6a98640 2116626637 S Ci:007:00 s 81 06 2200 0000 005a 90 <
f6a98640 2116627955 C Ci:007:00 0 26 = 050d0901 a1010920 75081500
26ff0095 01810209 20954091 02c0
At this point, the tablet starts talking.
f6a98640 2116651413 S Ii:007:01 -115 1 <
f6a98640 2116699959 C Ii:007:01 -2 0
f6a98640 2116703342 S Ii:007:01 -115 1 <
f6a98640 2116753323 C Ii:007:01 -2 0
f6a98640 2116756445 S Ii:007:01 -115 1 <
f6a98640 2116803284 C Ii:007:01 -2 0
f6a98640 2116804907 S Ii:007:01 -115 1 <
f6a98640 2116853281 C Ii:007:01 -2 0
... ad infinitum
Any ideas? I'm burned out for the day.
-Zapp
On Feb 9, 2008 11:59 AM, Magnus Vigerlöf <Magnus.Vigerlof@...> wrote:
> On lördag 09 februari 2008, Andrew Zappacky wrote:
> > Ok, I'm now at a wall. I added a chunk to the top of
> > wacom_init_input_dev that prints out all of the details from the
> > wacom_wac features struct, and here's what my dmesg looks like.
> >
> > I loaded the module, and this is what printed out:
> >
> > /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Input device:
> > /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Name:
> > <NULL> /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c:
> > Pktlen: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: X
> > Max: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Y
> > Max: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c:
> > Pressure Max: 0
> > /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Distance
> > Max: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c:
> > Type: 0 input: Unspecified device as
> > /devices/pci0000:00/0000:00:0b.1/usb1/1-2/1-2.3/1-2.3:1.0/input/input6
>
> The driver contains the hard-coded max-values for all tablets, so finding out
> these values would be part of the work. You'll have to fake these at first.
>
> [...]
> > During initial module loading, when it says "USB disconnect", my 0093
> > device disappears and then is replaced by the 0094 device.
> >
> > I've got no idea where to go from here. Perhaps the generic wacom
> > interface that this driver uses isn't the same as the ones the other
> > devices are using? Without interface specs on my tablet, I'm at the
> > fringes of my experience, I've never reverse-engineered hardware
> > before.
>
> What you probably need to do is get the tablet to talk, if doing this is
> different from the other USB-tablets then it will be more difficult. However,
> it's worth checking if the normal USB-code that exist in the driver works.
>
> Once the tablet is talking, you can just print out the USB packages in hex and
> start to map which bits are changing when you move the stylus, press the tip,
> use different tools, buttons, what happens when your stylus go out-of-prox,
> etc. Currently the longest message from the tablets are 10 bytes, so it's a
> very limited amount af bits to map. This step should also provide you with
> the max values of the reported axis so you can fill in the feature-struct.
>
> When you have a map of how the bits seems to change, you should see if there's
> any of the current decoders that fit that pattern. If there isn't you'll have
> to write a new one that does the tablet->Kernel input record conversion...
>
> Cheers
> Magnus
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
---------- Forwarded message ----------
From: Andrew Zappacky <zappacky@...>
Date: Feb 9, 2008 7:53 PM
Subject: Re: [Linuxwacom-devel] Getting USB TabletPCs supported (f.ex. Asus R1F)
To: Magnus Vigerlöf <Magnus.Vigerlof@...>
I've tried everything and I simply can not get the tablet to talk to me.
I opened up windows xp in KVM and usb-sniffed it until the tablet
started talking (oddly, the tablet didn't work in the vm). I then
edited the wacom driver to send the same sequence of packets, no
matter what combination of packets i sent, the tablet came back with
error -32 and didn't talk. I don't know how I should modify these
packets, I am pasting the output from the usbmonitor from the VM so
perhaps somebody could give me a hand.
f6db0340 2106737586 S Ci:007:00 s 80 08 0000 0000 0001 1 <
f6db0340 2106737763 C Ci:007:00 0 1 = 01
f6db0340 2106737774 S Ci:007:00 s 81 0a 0000 0000 0001 1 <
f6db0340 2106737885 C Ci:007:00 0 1 = 00
f6a98640 2116336662 S Ci:007:00 s 80 06 0100 0000 0040 64 <
f6a98640 2116336977 C Ci:007:00 0 18 = 12010101 00000008 6a059400 01000000 0001
f6a98640 2116436650 S Ci:007:00 s 80 06 0100 0000 0012 18 <
f6a98640 2116436970 C Ci:007:00 0 18 = 12010101 00000008 6a059400 01000000 0001
f6a98640 2116456650 S Ci:007:00 s 80 06 0200 0000 0009 9 <
f6a98640 2116456966 C Ci:007:00 0 9 = 09022900 010100c0 00
f6a98640 2116473383 S Ci:007:00 s 80 06 0200 0000 00ff 255 <
f6a98640 2116473966 C Ci:007:00 0 41 = 09022900 010100c0 00090400
00020300 00000921 10010001 221a0007 05810308
f6a98640 2116506682 S Ci:007:00 s 80 06 0100 0000 0012 18 <
f6a98640 2116507089 C Ci:007:00 0 18 = 12010101 00000008 6a059400 01000000 0001
f6a98640 2116526643 S Ci:007:00 s 80 06 0200 0000 0009 9 <
f6a98640 2116526961 C Ci:007:00 0 9 = 09022900 010100c0 00
f6a98640 2116543364 S Ci:007:00 s 80 06 0200 0000 0029 41 <
f6a98640 2116543961 C Ci:007:00 0 41 = 09022900 010100c0 00090400
00020300 00000921 10010001 221a0007 05810308
f6a98640 2116576637 S Co:007:00 s 00 09 0001 0000 0000 0
f6a98640 2116576833 C Co:007:00 0 0
f6a98640 2116619966 S Co:007:00 s 21 0a 0000 0000 0000 0
f6a98640 2116620081 C Co:007:00 0 0
f6a98640 2116626637 S Ci:007:00 s 81 06 2200 0000 005a 90 <
f6a98640 2116627955 C Ci:007:00 0 26 = 050d0901 a1010920 75081500
26ff0095 01810209 20954091 02c0
At this point, the tablet starts talking.
f6a98640 2116651413 S Ii:007:01 -115 1 <
f6a98640 2116699959 C Ii:007:01 -2 0
f6a98640 2116703342 S Ii:007:01 -115 1 <
f6a98640 2116753323 C Ii:007:01 -2 0
f6a98640 2116756445 S Ii:007:01 -115 1 <
f6a98640 2116803284 C Ii:007:01 -2 0
f6a98640 2116804907 S Ii:007:01 -115 1 <
f6a98640 2116853281 C Ii:007:01 -2 0
... ad infinitum
Any ideas? I'm burned out for the day.
-Zapp
On Feb 9, 2008 11:59 AM, Magnus Vigerlöf <Magnus.Vigerlof@...> wrote:
> On lördag 09 februari 2008, Andrew Zappacky wrote:
> > Ok, I'm now at a wall. I added a chunk to the top of
> > wacom_init_input_dev that prints out all of the details from the
> > wacom_wac features struct, and here's what my dmesg looks like.
> >
> > I loaded the module, and this is what printed out:
> >
> > /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Input device:
> > /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Name:
> > <NULL> /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c:
> > Pktlen: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: X
> > Max: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Y
> > Max: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c:
> > Pressure Max: 0
> > /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Distance
> > Max: 0 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c:
> > Type: 0 input: Unspecified device as
> > /devices/pci0000:00/0000:00:0b.1/usb1/1-2/1-2.3/1-2.3:1.0/input/input6
>
> The driver contains the hard-coded max-values for all tablets, so finding out
> these values would be part of the work. You'll have to fake these at first.
>
> [...]
> > During initial module loading, when it says "USB disconnect", my 0093
> > device disappears and then is replaced by the 0094 device.
> >
> > I've got no idea where to go from here. Perhaps the generic wacom
> > interface that this driver uses isn't the same as the ones the other
> > devices are using? Without interface specs on my tablet, I'm at the
> > fringes of my experience, I've never reverse-engineered hardware
> > before.
>
> What you probably need to do is get the tablet to talk, if doing this is
> different from the other USB-tablets then it will be more difficult. However,
> it's worth checking if the normal USB-code that exist in the driver works.
>
> Once the tablet is talking, you can just print out the USB packages in hex and
> start to map which bits are changing when you move the stylus, press the tip,
> use different tools, buttons, what happens when your stylus go out-of-prox,
> etc. Currently the longest message from the tablets are 10 bytes, so it's a
> very limited amount af bits to map. This step should also provide you with
> the max values of the reported axis so you can fill in the feature-struct.
>
> When you have a map of how the bits seems to change, you should see if there's
> any of the current decoders that fit that pattern. If there isn't you'll have
> to write a new one that does the tablet->Kernel input record conversion...
>
> Cheers
> Magnus
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
« Return to Thread: Getting USB TabletPCs supported (f.ex. Asus R1F)
| Free embeddable forum powered by Nabble | Forum Help |
