it appears the data is getting through to the inputdump tool, and is even
displayed, kind of.
The problem seems to be that the query for the event type/data format doesn't
result in the correct values, i.e. part of the data are wrongly normalized.
Evidence for this is the following snipped of output I get from running
'inputdump -i /dev/input/event0 -s':
Command: GetDevInfo: short='edev' long='Linux Evdev'
axes=-1 buttons=-1 generate=0x003ffe
Command: GetDevInfo: (empty query)
Command: GetValInfo: (empty query)
Command: GetValInfo: (empty query)
i.e. neither the number of axes nor the number of buttons could be determined,
not to speak of the respective range info data. Here is what the evtest tool
Justin referred to generated when running 'evtest /dev/input/event0':
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x56a product 0x21 version 0x101
Input device name: "Wacom Intuos 6x8"
Supported events:
Event type 1 (Key)
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 326 (ToolMouse)
Event code 327 (ToolLens)
Event code 330 (Touch)
Event code 331 (Stylus)
Event code 332 (Stylus2)
Event type 3 (Absolute)
Event code 0 (X)
Value 456
Min 0
Max 20320
Fuzz 4
Event code 1 (Y)
Value 832
Min 0
Max 15040
Fuzz 4
Event code 5 (Rz)
Value 0
Min -900
Max 899
Event code 6 (Throttle)
Value 0
Min -1023
Max 1023
Event code 24 (Pressure)
Value 3
Min 0
Max 1023
Event code 25 (Distance)
Value 10
Min 0
Max 15
Event code 26 (XTilt)
Value 59
Min 0
Max 127
Event code 27 (YTilt)
Value 56
Min 0
Max 127
I'm now trying to figure out what the evtest does differently compared to GII...
Regards, Stefan
