MobileRead Forums - View Single Post - Using the wacom interface of the DR1000S to control a Windows machine

Cliffe · 06-06-2009, 05:30 AM

How can we use the wacom interface of the DR1000S to control a Windows machine?

I have been looking at this for the last couple of hours because I think it may be possible. However, I can’t afford to spend any more time on it at the moment so I thought I would share what I have found and maybe someone else can give it a shot.

I guess the steps involved would be to
1: find the wacom driver files
2: find a way of sending all the relevant information via the mini usb
3: interpret that information on the windows side of things
Note: this may all be a wild goose chase if wacom don’t have *compatible* Windows drivers to handle that last step.

Doing this sort of thing would be much quicker if there was a port of a console program such as xterm.

Step 1: find the wacom driver files

From /proc/bus/devices:

I: Bus=0013 Vendor=0020 Product=0001 Version=0100
N: Name="iOn Keyboard"
P: Phys=ttymxc3/serio0/input0
S: Sysfs=/class/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=100003
B: KEY=3fc0 0 8000400 10004000

The device file is:
/dev/input/event0

Interestingly the vendor number does not match any in:
PCI and AGP Vendors, Devices and Subsystems identification file.
http://www.clavister.com/support/utilities/vendors.txt
or
List of USB ID's
http://www.linux-usb.org/usb.ids

Step 2: find a way of sending all the relevant information via the mini usb

I hoped this would be as simple as redirecting /dev/input/event0 to a file representing the usb. There are a few more steps than that.

USB always has a host and a client. The Reader is the client.

Currently the Reader uses the mini usb for making the card available to the host.

Resources:
http://www.linux-usb.org/gadget/
http://liyiadam.blogspot.com/2006/12/usb-gadget.html
https://wiki.ubuntu.com/MobileAndEmbedded/USBClient

So I guess after the user says “No” (I am not connecting to the computer to manage my files), then (based on that first link) we might be able to use gadgetfs to avoid having to write a kernel module: (mount -t gadgetfs gadgetfs /dev/gadget) and use that to send the wacom information. Perhaps with: /dev/input/event0 > /dev/gadget/[whatever file represents the usb]

Keeping in mind:
The kernel would need the gadgetfs module compiled and loaded (loading: modprobe gadgetfs).
It may be necessary to make sure the vender id etc match a known wacom USB ids.
There may be a few steps for setting up the gadget.
I think /dev/loop/0 and /mnt/card may be used for the current sharing of the SD card.

Step 3: interpret that information on the windows side of things

If we are lucky and the information is in the form which is output from other wacom tablets then, hey presto, we should be in business. It may simply be possible to alter the device id info to match a wacom product. If not then well, writing a driver could be hard. But if it is standard and we can trick it into thinking it is another wacom model then that would be cool!

It would be great if someone else would give this a go!

Cheers,

Cliffe.

06-06-2009, 05:30 AM	#1
Cliffe Member Posts: 10 Karma: 45 Join Date: Apr 2009 Device: DR1000S	Using the wacom interface of the DR1000S to control a Windows machine How can we use the wacom interface of the DR1000S to control a Windows machine? I have been looking at this for the last couple of hours because I think it may be possible. However, I can’t afford to spend any more time on it at the moment so I thought I would share what I have found and maybe someone else can give it a shot. I guess the steps involved would be to 1: find the wacom driver files 2: find a way of sending all the relevant information via the mini usb 3: interpret that information on the windows side of things Note: this may all be a wild goose chase if wacom don’t have compatible Windows drivers to handle that last step. Doing this sort of thing would be much quicker if there was a port of a console program such as xterm. Step 1: find the wacom driver files From /proc/bus/devices: I: Bus=0013 Vendor=0020 Product=0001 Version=0100 N: Name="iOn Keyboard" P: Phys=ttymxc3/serio0/input0 S: Sysfs=/class/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=100003 B: KEY=3fc0 0 8000400 10004000 The device file is: /dev/input/event0 Interestingly the vendor number does not match any in: PCI and AGP Vendors, Devices and Subsystems identification file. http://www.clavister.com/support/utilities/vendors.txt or List of USB ID's http://www.linux-usb.org/usb.ids Step 2: find a way of sending all the relevant information via the mini usb I hoped this would be as simple as redirecting /dev/input/event0 to a file representing the usb. There are a few more steps than that. USB always has a host and a client. The Reader is the client. Currently the Reader uses the mini usb for making the card available to the host. Resources: http://www.linux-usb.org/gadget/ http://liyiadam.blogspot.com/2006/12/usb-gadget.html https://wiki.ubuntu.com/MobileAndEmbedded/USBClient So I guess after the user says “No” (I am not connecting to the computer to manage my files), then (based on that first link) we might be able to use gadgetfs to avoid having to write a kernel module: (mount -t gadgetfs gadgetfs /dev/gadget) and use that to send the wacom information. Perhaps with: /dev/input/event0 > /dev/gadget/[whatever file represents the usb] Keeping in mind: The kernel would need the gadgetfs module compiled and loaded (loading: modprobe gadgetfs). It may be necessary to make sure the vender id etc match a known wacom USB ids. There may be a few steps for setting up the gadget. I think /dev/loop/0 and /mnt/card may be used for the current sharing of the SD card. Step 3: interpret that information on the windows side of things If we are lucky and the information is in the form which is output from other wacom tablets then, hey presto, we should be in business. It may simply be possible to alter the device id info to match a wacom product. If not then well, writing a driver could be hard. But if it is standard and we can trick it into thinking it is another wacom model then that would be cool! It would be great if someone else would give this a go! Cheers, Cliffe. Last edited by Cliffe; 06-06-2009 at 05:36 AM.