The output from kernel looks reasonable to me (note: I do not have
such a tablet to compare to).
I notice that on initial touch the values jump a little bit. I don't
see any averaging logic to smooth that out in kernel or
xf86-input-wacom which is a little surprising...but thats a different
topic.
I did look further back in stack of xf86-input-wacom from my previous
mention and I see a secondary level were it assumes a value of zero
only when scroll ring is out-of-proxity (in sendCommonEvent()).
759 v5 = ds->abswheel;
871 if (v3 || v4 || v5 || buttons || ds->relwheel)
872 {
873 sendCommonEvents(pInfo, ds, x, y, z, v3, v4, v5);
So this looks to me like a X side bug that is samewhat new when their
values were normalized.
Hopefully Ping or Peter can offer a proper fix.
Chris
On Thu, Aug 26, 2010 at 12:09 PM, holzminister
<[email protected]> wrote:
> No problem, here comes the next try:
>
> Scrolling down:
>
> Event: time 1282842084.764066, type 3 (Absolute), code 8 (Wheel), value 26
> Event: time 1282842084.764073, type 4 (Misc), code 0 (Serial), value -1
> Event: time 1282842084.764076, -------------- Report Sync ------------
> Event: time 1282842084.812060, type 3 (Absolute), code 8 (Wheel), value 27
> Event: time 1282842084.812066, type 4 (Misc), code 0 (Serial), value -1
> Event: time 1282842084.812068, -------------- Report Sync ------------
> Event: time 1282842084.840061, type 3 (Absolute), code 8 (Wheel), value 26
> Event: time 1282842084.840067, type 4 (Misc), code 0 (Serial), value -1
> Event: time 1282842084.840070, -------------- Report Sync ------------
> Event: time 1282842084.864058, type 3 (Absolute), code 8 (Wheel), value 27
> Event: time 1282842084.864063, type 4 (Misc), code 0 (Serial), value -1
> Event: time 1282842084.864065, -------------- Report Sync ------------
> Event: time 1282842085.388054, type 3 (Absolute), code 8 (Wheel), value 28
> Event: time 1282842085.388060, type 4 (Misc), code 0 (Serial), value -1
> Event: time 1282842085.388064, -------------- Report Sync ------------
> Event: time 1282842085.488054, type 3 (Absolute), code 8 (Wheel), value 29
> Event: time 1282842085.488060, type 4 (Misc), code 0 (Serial), value -1
> Event: time 1282842085.488064, -------------- Report Sync ------------
> Event: time 1282842086.064042, type 3 (Absolute), code 8 (Wheel), value 0
> Event: time 1282842086.064049, type 1 (Key), code 325 (ToolFinger), value 0
> Event: time 1282842086.064051, type 3 (Absolute), code 40 (Misc), value 0
> Event: time 1282842086.064053, type 4 (Misc), code 0 (Serial), value -1
> Event: time 1282842086.064056, -------------- Report Sync ------------
>
>
> Something interesting to see? :)
>
>
> Best regards,
> EH
>
>
>
>
> Am Thu, 26 Aug 2010 11:04:30 -0500
> schrieb Chris Bagwell <[email protected]>:
>
>> Opps, we forgot to mention important fact. You need to switch your
>> console away from X for evtest to be able to see the events.
>>
>> When its working right, you'll see printing to the screen as you use
>> tablet.
>>
>> Chris
>>
>> On Thu, Aug 26, 2010 at 11:02 AM, holzminister
>> <[email protected]> wrote:
>> > Hi!
>> >
>> > I don't know how wrong output should look like, so I I have to give
>> > you the full one:
>> >
>> > #####
>> > Input driver version is 1.0.0
>> > Input device ID: bus 0x3 vendor 0x56a product 0xb9 version 0x104
>> > Input device name: "Wacom Intuos4 6x9"
>> > Supported events:
>> > Event type 0 (Sync)
>> > Event type 1 (Key)
>> > Event code 256 (Btn0)
>> > Event code 257 (Btn1)
>> > Event code 258 (Btn2)
>> > Event code 259 (Btn3)
>> > Event code 260 (Btn4)
>> > Event code 261 (Btn5)
>> > Event code 262 (Btn6)
>> > Event code 263 (Btn7)
>> > Event code 264 (Btn8)
>> > Event code 272 (LeftBtn)
>> > Event code 273 (RightBtn)
>> > Event code 274 (MiddleBtn)
>> > Event code 275 (SideBtn)
>> > Event code 276 (ExtraBtn)
>> > Event code 320 (ToolPen)
>> > Event code 321 (ToolRubber)
>> > Event code 322 (ToolBrush)
>> > Event code 323 (ToolPencil)
>> > Event code 324 (ToolAirbrush)
>> > Event code 325 (ToolFinger)
>> > Event code 326 (ToolMouse)
>> > Event code 327 (ToolLens)
>> > Event code 330 (Touch)
>> > Event code 331 (Stylus)
>> > Event code 332 (Stylus2)
>> > Event type 2 (Relative)
>> > Event code 8 (Wheel)
>> > Event type 3 (Absolute)
>> > Event code 0 (X)
>> > Value 0
>> > Min 0
>> > Max 44704
>> > Fuzz 4
>> > Event code 1 (Y)
>> > Value 0
>> > Min 0
>> > Max 27940
>> > Fuzz 4
>> > Event code 2 (Z)
>> > Value 0
>> > Min -900
>> > Max 899
>> > Event code 5 (Rz)
>> > Value 0
>> > Min -900
>> > Max 899
>> > Event code 6 (Throttle)
>> > Value 0
>> > Min -1023
>> > Max 1023
>> > Event code 8 (Wheel)
>> > Value 0
>> > Min 0
>> > Max 1023
>> > Event code 24 (Pressure)
>> > Value 0
>> > Min 0
>> > Max 2047
>> > Event code 25 (Distance)
>> > Value 0
>> > Min 0
>> > Max 63
>> > Event code 26 (XTilt)
>> > Value 0
>> > Min 0
>> > Max 127
>> > Event code 27 (YTilt)
>> > Value 0
>> > Min 0
>> > Max 127
>> > Event code 40 (Misc)
>> > Value 0
>> > Min 0
>> > Max 0
>> > Event type 4 (Misc)
>> > Event code 0 (Serial)
>> > Testing ... (interrupt to exit)
>> > ^C
>> > #####
>> >
>> > I left the program running for some time while using the board, but
>> > the output didn't change anymore.
>> >
>> > Hope you can see something in these lines!
>> >
>> > EH
>> >
>> >
>> >
>> > Am Thu, 26 Aug 2010 11:06:11 +0200
>> > schrieb Ping Cheng <[email protected]>:
>> >
>> >> I feel it is a bug in the kernel driver. But I don't have time to
>> >> test it. Can you run evtest
>> >> (http://cgit.freedesktop.org/~whot/evtest/commit/) to see if the
>> >> data was reported wrong from the kernel or not?
>> >>
>> >> Thank you.
>> >>
>> >> Ping
>> >>
>> >> On Tue, Aug 24, 2010 at 2:21 AM, holzminister
>> >> <[email protected]> wrote:
>> >> > Hi everybody!
>> >> >
>> >> > I thought it's time to post another problem with the scroll
>> >> > wheel of the intuos4. :)
>> >> >
>> >> > When I lift my finger from the wheel after scrolling it sends one
>> >> > signal to scroll up. For example I scroll five steps down, the
>> >> > wheel scrolls back one step. When I scroll five steps up, the
>> >> > same happens: The wheel increases it to six steps.
>> >> >
>> >> > My setup:
>> >> > * Gentoo Linux with kernel 2.6.34
>> >> > * Wacom driver:
>> >> > - xf86-input-wacom 0.10.8
>> >> > - linuxwacom-0.8.8-8 for the kernel module
>> >> > * Xorg-Server 1.7.7 with hal (fdi)
>> >> >
>> >> >
>> >> > Does anyone notice the same or could help?
>> >> >
>> >> > Best regards,
>> >> > EH
>> >> >
>> >> >
>> >> > PS. Here are the last lines of what xev gives me:
>> >> >
>> >> > ButtonPress event, serial 33, synthetic NO, window 0x3e00001,
>> >> > root 0xbd, subw 0x0, time 3207015, (89,93), root:(967,1080),
>> >> > state 0x0, button 5, same_screen YES
>> >> >
>> >> > ButtonRelease event, serial 33, synthetic NO, window 0x3e00001,
>> >> > root 0xbd, subw 0x0, time 3207015, (89,93), root:(967,1080),
>> >> > state 0x1000, button 5, same_screen YES
>> >> >
>> >> > MotionNotify event, serial 33, synthetic NO, window 0x3e00001,
>> >> > root 0xbd, subw 0x0, time 3207015, (89,93), root:(967,1080),
>> >> > state 0x0, is_hint 0, same_screen YES
>> >> >
>> >> > ButtonPress event, serial 33, synthetic NO, window 0x3e00001,
>> >> > root 0xbd, subw 0x0, time 3207091, (89,93), root:(967,1080),
>> >> > state 0x0, button 4, same_screen YES
>> >> >
>> >> > ButtonRelease event, serial 33, synthetic NO, window 0x3e00001,
>> >> > root 0xbd, subw 0x0, time 3207091, (89,93), root:(967,1080),
>> >> > state 0x800, button 4, same_screen YES
>> >> >
>> >> > MotionNotify event, serial 33, synthetic NO, window 0x3e00001,
>> >> > root 0xbd, subw 0x0, time 3207091, (89,93), root:(967,1080),
>> >> > state 0x0, is_hint 0, same_screen YES
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > Sell apps to millions through the Intel(R) Atom(Tm) Developer
>> >> > Program Be part of this innovative community and reach millions
>> >> > of netbook users worldwide. Take advantage of special
>> >> > opportunities to increase revenue and speed time-to-market. Join
>> >> > now, and jumpstart your future.
>> >> > http://p.sf.net/sfu/intel-atom-d2d
>> >> > _______________________________________________
>> >> > Linuxwacom-discuss mailing list
>> >> > [email protected]
>> >> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >> >
>> >
>> > ------------------------------------------------------------------------------
>> > Sell apps to millions through the Intel(R) Atom(Tm) Developer
>> > Program Be part of this innovative community and reach millions of
>> > netbook users worldwide. Take advantage of special opportunities to
>> > increase revenue and speed time-to-market. Join now, and jumpstart
>> > your future. http://p.sf.net/sfu/intel-atom-d2d
>> > _______________________________________________
>> > Linuxwacom-discuss mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
