Dixit "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> : > When you use a wacom.c from an earlier version than 0.7.4-2, did your > Volito1 work properly? > Yes. With a 2.6.8 kernel, and the following wacom driver versions : 0.7.0 : works, wacdump reports consistent behaviour (pressure, position, etc) 0.7.2 : works the same 0.7.3-1 : is detected, but no event appears in wacdump 0.7.4-2 : same as 0.7.3-1
I added 0.7.3-1 because I figured it would help find the problematic piece(s) of code. > The reason that we added the line back (it was there before and then > someone removed it thinking that data[0] != 2 should take care of it) was: > > For Graphire (Volito as well) tablets, the only valid event type is 2. If > wacom.c receives any other event type (data[0]), it means that the data is > not a Wacom specific event. So we check if data[0] != 2 or not. For > Volito, we often get 99s. When a 99 is received, we don't want it to call > usb_summit_urb. That's why the statement followed by a return > immediately. > Well it makes sense (if at least I knew what usb_summit_urb did ;-) > You can comment out the "for Volito" if-statement in 0.7.4-2 code to see > if the driver works or not. I bet it won't work since the problem isn't > in that routine. It is somewhere in the startup or/and setup stage where > the tablet started by sending none-Wacom specific event. > Well, it looks like you just lost your bet ;-). I tried with the 0.7.4-2 version of the driver with the if-statement commented, with the 2.6.16 kernel, and wacdump sees the events sent by the tablet, and the events are consistent (pressure, position, button, etc) Now, I shall try it some time with increasing the verbosity of kernel logs, to see if that plethora of 99s happens with my volito1. If you need someone to test things related to volito1 tablets, think of me... _______________________________________________ Linuxwacom-discuss mailing list Linuxwacom-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
