« Return to Thread: Getting USB TabletPCs supported (f.ex. Asus R1F)
Re: Getting USB TabletPCs supported (f.ex. Asus R1F)
by Magnus Vigerlöf-2
::
Rate this Message:
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
> 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 |
