|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
Getting USB TabletPCs supported (f.ex. Asus R1F)Hi list!
I recently got an Asus R1F and am now facing the problem that the Wacom device built into this notebook is currently not supported on Linux. I read over nearly all available sources of information (mailing list archives, etc.) and by now the only information I got is that "it is currently not on the todo list" plus some ideas how we could get it work. As some of the postings are quite old (~8 months or more), I just wanted to ask if there's been any progress on this by now? I'm definetly willing to offer some time, efforts, whatever to get this working. I'd call myself an averagely skilled C developer with some experiences in driver and kernel development and would like to help with getting this device supported. Maybe we could some up all ideas so far (I found some threads talking about changing some IDs, etc. in the current source code) in this thread to share our current knowledge about this device and the wacom driver support for it. >From what I've tried by now, I'm not getting any events from the touchpanel by querying the /dev/input/event* devices so I'm almost at the beginning of getting the bits together. Thanks in advance for any insights, pointers, ideas... ciao, -- | .-. | Alexander Griesser -- <private@...> | .''`. | | /v\ \ http://www.tuxx-home.at/ / : :' : | | /( )\ | GPG-KeyID: 0xA2949B5A | `. `' | | ^^ ^^ `-------------------------------------------------' `- | ------------------------------------------------------------------------- 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 |
|
|
Re: Getting USB TabletPCs supported (f.ex. Asus R1F)I suspect that my laptop and your laptop use the same model of
touchscreen. I changed the device IDs in the current source code to allow for my model, and the result was that it recognized the screen, but the event device (which showed up!) gave nothing but garbage to wacdump. I suspect that this means some more coding will need to be done. On Feb 7, 2008 1:51 AM, Alexander Griesser <work@...> wrote: > Hi list! > > I recently got an Asus R1F and am now facing the problem that the Wacom > device built into this notebook is currently not supported on Linux. > > I read over nearly all available sources of information (mailing list > archives, etc.) and by now the only information I got is that "it is > currently not on the todo list" plus some ideas how we could get it > work. > > As some of the postings are quite old (~8 months or more), I just wanted > to ask if there's been any progress on this by now? > > I'm definetly willing to offer some time, efforts, whatever to get this > working. I'd call myself an averagely skilled C developer with some > experiences in driver and kernel development and would like to help with > getting this device supported. > > Maybe we could some up all ideas so far (I found some threads talking > about changing some IDs, etc. in the current source code) in this thread > to share our current knowledge about this device and the wacom driver > support for it. > > >From what I've tried by now, I'm not getting any events from the > touchpanel by querying the /dev/input/event* devices so I'm almost at > the beginning of getting the bits together. > > Thanks in advance for any insights, pointers, ideas... > > ciao, > -- > | .-. | Alexander Griesser -- <private@...> | .''`. | > | /v\ \ http://www.tuxx-home.at/ / : :' : | > | /( )\ | GPG-KeyID: 0xA2949B5A | `. `' | > | ^^ ^^ `-------------------------------------------------' `- | > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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 |
|
|
Re: Getting USB TabletPCs supported (f.ex. Asus R1F)On fredag 08 februari 2008, Andrew Zappacky wrote:
> I suspect that my laptop and your laptop use the same model of > touchscreen. I changed the device IDs in the current source code to > allow for my model, and the result was that it recognized the screen, > but the event device (which showed up!) gave nothing but garbage to > wacdump. I suspect that this means some more coding will need to be > done. > > On Feb 7, 2008 1:51 AM, Alexander Griesser <work@...> wrote: > > Hi list! > > > > I recently got an Asus R1F and am now facing the problem that the Wacom > > device built into this notebook is currently not supported on Linux. > > > > I read over nearly all available sources of information (mailing list > > archives, etc.) and by now the only information I got is that "it is > > currently not on the todo list" plus some ideas how we could get it > > work. > > > > As some of the postings are quite old (~8 months or more), I just wanted > > to ask if there's been any progress on this by now? I'd actually dare to say very little.. It all probably comes down to access to hardware, to some extent documentation, to some extent skill in reverse engineering the protocol used, and of course time to put time into this. > > I'm definetly willing to offer some time, efforts, whatever to get this > > working. I'd call myself an averagely skilled C developer with some > > experiences in driver and kernel development and would like to help with > > getting this device supported. > > > > Maybe we could some up all ideas so far (I found some threads talking > > about changing some IDs, etc. in the current source code) in this thread > > to share our current knowledge about this device and the wacom driver > > support for it. The following feature request contains some information (just so we have a connection from this thread to it): https://sourceforge.net/tracker/index.php?func=detail&aid=1593330&group_id=69596&atid=525127 > > From what I've tried by now, I'm not getting any events from the > > touchpanel by querying the /dev/input/event* devices so I'm almost at > > the beginning of getting the bits together. > > > > Thanks in advance for any insights, pointers, ideas... Personally I'm investing my time into the hotplugger client program, but it would be nice to see these TabletPCs become supported as well (less to blacklist for me). As I lack pretty much everything to work with these, I'm afraid I can more or less only help out to review code... When you start producing patches on the driver, I think it probably will be worth putting these into our git-repo [1] at once. Maybe not into master right away, but at least into a separate branch. This way this work can be made more visible, without actually affecting the normal driver development. Cheers Magnus [1] git://git.debian.org/git/collab-maint/linux-wacom.git [2] http://www.kernel.org/pub/software/scm/git/docs/user-manual.html ------------------------------------------------------------------------- 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 |
|
|
Re: Getting USB TabletPCs supported (f.ex. Asus R1F)Magnus Vigerlöf schrieb:
> On fredag 08 februari 2008, Andrew Zappacky wrote: >> I suspect that my laptop and your laptop use the same model of >> touchscreen. I changed the device IDs in the current source code to >> allow for my model, and the result was that it recognized the screen, >> but the event device (which showed up!) gave nothing but garbage to >> wacdump. I suspect that this means some more coding will need to be >> done. Could you provide a patch, code snippets, a listing of the changed files or something like this? >>> As some of the postings are quite old (~8 months or more), I just wanted >>> to ask if there's been any progress on this by now? > > I'd actually dare to say very little.. It all probably comes down to access to > hardware If SSH access to one of these machines is enough, I'm offering you exclusive root access to an Asus R1F at any time you want. > The following feature request contains some information (just so we have a > connection from this thread to it): > https://sourceforge.net/tracker/index.php?func=detail&aid=1593330&group_id=69596&atid=525127 Yeah, I know, thanks for linking it here. > When you start producing patches on the driver, I think it probably will be > worth putting these into our git-repo [1] at once. Maybe not into master > right away, but at least into a separate branch. This way this work can be > made more visible, without actually affecting the normal driver development. Good idea! ciao, Alex ------------------------------------------------------------------------- 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 |
|
|
Re: Getting USB TabletPCs supported (f.ex. Asus R1F)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 /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.1/input/input7 usbcore: registered new interface driver wacom /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_sys.c: v1.46-pc0.2:USB Wacom Graphire and Wacom Intuos tablet driver usb 1-2.3: USB disconnect, address 6 usb 1-2.3: new full speed USB device using ehci_hcd and address 7 usb 1-2.3: configuration #1 chosen from 1 choice /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: 4173141612 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Y Max: 4173138976 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Pressure Max: 4173137920 /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 I unloaded the module and then reloaded it: input: Unspecified device as /devices/pci0000:00/0000:00:0b.1/usb1/1-2/1-2.3/1-2.3:1.0/input/input8 usbcore: deregistering interface driver wacom /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: 4173141612 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Y Max: 4173138976 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Pressure Max: 4173137920 /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/input9 I repeated that process, and the output did not change: usbcore: registered new interface driver wacom /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_sys.c: v1.46-pc0.2:USB Wacom Graphire and Wacom Intuos tablet driver usbcore: deregistering interface driver wacom /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: 4173141612 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Y Max: 4173138976 /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_wac.c: Pressure Max: 4173137920 /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/input10 usbcore: registered new interface driver wacom /home/andrew/wacom/linuxwacom-0.7.9-7/src/2.6.24/wacom_sys.c: v1.46-pc0.2:USB Wacom Graphire and Wacom Intuos tablet driver 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. -Zapp On Feb 9, 2008 3:35 AM, Alexander Griesser <work@...> wrote: > Magnus Vigerlöf schrieb: > > On fredag 08 februari 2008, Andrew Zappacky wrote: > >> I suspect that my laptop and your laptop use the same model of > >> touchscreen. I changed the device IDs in the current source code to > >> allow for my model, and the result was that it recognized the screen, > >> but the event device (which showed up!) gave nothing but garbage to > >> wacdump. I suspect that this means some more coding will need to be > >> done. > > Could you provide a patch, code snippets, a listing of the changed files > or something like this? > > >>> As some of the postings are quite old (~8 months or more), I just wanted > >>> to ask if there's been any progress on this by now? > > > > I'd actually dare to say very little.. It all probably comes down to access to > > hardware > > If SSH access to one of these machines is enough, I'm offering you > exclusive root access to an Asus R1F at any time you want. > > > The following feature request contains some information (just so we have a > > connection from this thread to it): > > https://sourceforge.net/tracker/index.php?func=detail&aid=1593330&group_id=69596&atid=525127 > > Yeah, I know, thanks for linking it here. > > > When you start producing patches on the driver, I think it probably will be > > worth putting these into our git-repo [1] at once. Maybe not into master > > right away, but at least into a separate branch. This way this work can be > > made more visible, without actually affecting the normal driver development. > > Good idea! > > ciao, > Alex > ------------------------------------------------------------------------- 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 |
|
|
Re: Getting USB TabletPCs supported (f.ex. Asus R1F)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 |
|
|
|
|
|
Re: Fwd: Getting USB TabletPCs supported (f.ex. Asus R1F)On söndag 10 februari 2008, Andrew Zappacky wrote:
> 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. [...] > 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 Put the following code in wacom_probe just before the do-while with call to usb_get_report and see if that give you any result (found a bug in usb_get_report, it also returns -32 btw). {char testdata[128]; int testrval; testrval = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0), 13, USB_TYPE_CLASS | USB_RECIP_INTERFACE | USB_DIR_IN, 1, intf->altsetting[0].desc.bInterfaceNumber, testdata, 40, 1000); printk(KERN_INFO "Test msg: %d\n", testrval); if(testrval > 0) { int c = 0; printk(KERN_INFO "Received: "); for(; c<testrval; c++) printk("%02x", testdata[c]&0xff); printk("\n"); }} Hopefully it should show something familiar (it does on my Volito 2 at least). [...] > Any ideas? I'm burned out for the day. Change '13', USB_TYPE_CLASS, and USB_RECIP_INTERFACE and maybe some of the other params above. See what you get, and correlate it to the output you get. If you have another Wacom tablet (that actually is supported and works) use the usb-sniffer with that one too so you can see the differences. 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 |
| Free embeddable forum powered by Nabble | Forum Help |