You have been subscribed to a public bug:

Our scroll function of our interactive whiteboard doesn't work,
http://www.vmarker.org . When we use the scroll wheel, we have seen that
the correct HID reports are transmitted to the PC. You can see this in
the next example:

#sudo cat /dev/hidraw2 | xxd -c6
0000018: 0001 8402 7800  ....x.
000001e: 0001 8402 7800  ....x.
0000024: 00ff 8402 7800  ....x.
000002a: 00ff 8402 7800  ....x.

The build up of our HID reports is:
-First byte: bit 0 and bit 1 are left and right mouse button
-Second byte: is the scroll in relative axis (127 to -128)
-byte 3 and 4: is the X-axis in absolute coordinate (0 to 1023)
-byte 5 and 6: is the Y-axis in absolute coordinate (0 to 1023)

As you can see in the output of the command the PC receives the correct scroll 
values 1 (0x01) and -1(0xFF).
When I run the same command with a normal usb mouse I get similar output except 
the absolute coordinates.

Next thing I checked was if xorg correctly find and configured my
device.

    [  4010.530] (II) config/udev: Adding input device Vmarker by Robin Theunis 
VmarkerUSB v0.4 (/dev/input/event6)
    [  4010.530] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: Applying 
InputClass "evdev pointer catchall"
    [  4010.530] (II) Using input driver 'evdev' for 'Vmarker by Robin Theunis 
VmarkerUSB v0.4'
    [  4010.530] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [  4010.531] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: always reports 
core events
    [  4010.531] (**) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Device: 
"/dev/input/event6"
    [  4010.531] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Vendor 
0x2572 Product 0x8003
    [  4010.531] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 3 
mouse buttons
    [  4010.531] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 
scroll wheel(s)
    [  4010.531] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 
relative axes
    [  4010.531] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 
absolute axes
    [  4010.531] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found x 
and y absolute axes
    [  4010.531] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 
absolute touchscreen
    [  4010.531] (II) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
Configuring as touchscreen
    [  4010.531] (II) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Adding 
scrollwheel support
    [  4010.531] (**) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
YAxisMapping: buttons 4 and 5
    [  4010.531] (**) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [  4010.531] (**) Option "config_info" 
"udev:/sys/devices/pci0000:00/0000:00:06.0/usb2/2-2/2-2:1.1/input/input12/event6"
    [  4010.531] (II) XINPUT: Adding extended input device "Vmarker by Robin 
Theunis VmarkerUSB v0.4" (type: TOUCHSCREEN, id 12)
    [  4010.531] (WW) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
touchpads, tablets and touchscreens ignore relative axes.
    [  4010.531] (II) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
initialized for absolute axes.
    [  4010.531] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) keeping 
acceleration scheme 1
    [  4010.531] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) 
acceleration profile 0
    [  4010.531] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) 
acceleration factor: 2.000
    [  4010.531] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) 
acceleration threshold: 4
    [  4010.539] (II) config/udev: Adding input device Vmarker by Robin Theunis 
VmarkerUSB v0.4 (/dev/input/mouse2)
    [  4010.539] (II) No input driver specified, ignoring this device.
    [  4010.539] (II) This device may have been added with another device file.
    [  4010.567] (II) config/udev: Adding input device Vmarker by Robin Theunis 
VmarkerUSB v0.4 (/dev/input/mouse3)
    [  4010.567] (II) No input driver specified, ignoring this device.
    [  4010.567] (II) This device may have been added with another device file.
    [  4010.568] (II) config/udev: Adding input device Vmarker by Robin Theunis 
VmarkerUSB v0.4 (/dev/input/event7)
    [  4010.568] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: Applying 
InputClass "evdev pointer catchall"
    [  4010.568] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: Applying 
InputClass "evdev keyboard catchall"
    [  4010.568] (II) Using input driver 'evdev' for 'Vmarker by Robin Theunis 
VmarkerUSB v0.4'
    [  4010.568] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [  4010.568] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: always reports 
core events
    [  4010.568] (**) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Device: 
"/dev/input/event7"
    [  4010.568] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Vendor 
0x2572 Product 0x8003
    [  4010.568] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 3 
mouse buttons
    [  4010.568] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 
relative axes
    [  4010.568] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found x 
and y relative axes
    [  4010.568] (--) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: Found 
keys
    [  4010.568] (II) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
Configuring as mouse
    [  4010.568] (II) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
Configuring as keyboard
    [  4010.568] (**) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
YAxisMapping: buttons 4 and 5
    [  4010.568] (**) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [  4010.568] (**) Option "config_info" 
"udev:/sys/devices/pci0000:00/0000:00:06.0/usb2/2-2/2-2:1.3/input/input13/event7"
    [  4010.568] (II) XINPUT: Adding extended input device "Vmarker by Robin 
Theunis VmarkerUSB v0.4" (type: KEYBOARD, id 13)
    [  4010.568] (**) Option "xkb_rules" "evdev"
    [  4010.568] (**) Option "xkb_model" "pc105"
    [  4010.568] (**) Option "xkb_layout" "be"
    [  4010.568] (II) evdev: Vmarker by Robin Theunis VmarkerUSB v0.4: 
initialized for relative axes.
    [  4010.570] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) keeping 
acceleration scheme 1
    [  4010.570] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) 
acceleration profile 0
    [  4010.570] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) 
acceleration factor: 2.000
    [  4010.570] (**) Vmarker by Robin Theunis VmarkerUSB v0.4: (accel) 
acceleration threshold: 4
    [  4010.583] (II) config/udev: Adding input device Vmarker by Robin Theunis 
VmarkerUSB v0.4 (/dev/input/js2)
    [  4010.583] (II) No input driver specified, ignoring this device.
    [  4010.583] (II) This device may have been added with another device file.

You can see that xorg correctly found my device. I can narrow down the
problem to /dev/input/event6 in my case. I can make out of this info
that xorg correctly found the axis and configured them.

With  #sudo cat /dev/input/event6 | xxd -c48 I checked if xorg is reporting the 
correct data.
    0000000: c517 a84f 0000 0000 9bab 0d00 0000 0000 0200 0800 ffff ffff c517 
a84f 0000 0000 a0ab 0d00 0000 0000 0000 0000 0000 0000  
...O.......................O....................
    0000030: c617 a84f 0000 0000 c9bc 0000 0000 0000 0200 0800 0100 0000 c617 
a84f 0000 0000 cebc 0000 0000 0000 0000 0000 0000 0000  
...O.......................O....................
    0000060: c617 a84f 0000 0000 606c 0100 0000 0000 0200 0800 0100 0000 c617 
a84f 0000 0000 626c 0100 0000 0000 0000 0000 0000 0000  
...O....`l.................O....bl..............
    0000090: c617 a84f 0000 0000 67c1 0300 0000 0000 0200 0800 0100 0000 c617 
a84f 0000 0000 6cc1 0300 0000 0000 0000 0000 0000 0000  
...O....g..................O....l...............
    00000c0: c717 a84f 0000 0000 7749 0000 0000 0000 0200 0800 ffff ffff c717 
a84f 0000 0000 7c49 0000 0000 0000 0000 0000 0000 0000  
...O....wI.................O....|I..............
    00000f0: c717 a84f 0000 0000 99a1 0000 0000 0000 0200 0800 ffff ffff c717 
a84f 0000 0000 f3a1 0000 0000 0000 0000 0000 0000 0000  
...O.......................O....................

I can perfectly view the scroll data, in 32bit format. the -1(ffff ffff)
and 1 (0100 0000) in the stream. I cross checked this with my normal usb
mouse and I get the same information, but a working scroll function.

The scroll function works on:
-ubuntu 11.10, 11.04, 10.10, ... (only 64bit tested)
-debian 6.0 (32bit and 64bit)
-windows XP, vista, 7 (32bit and 64bit)
-mac osx 10.6 and 10.7

Uname -a for the debian (my reference machine)
Linux vmarkerdev 3.2.0-2-amd64 #1 SMP Tue Mar 20 18:36:37 UTC 2012 x86_64 
GNU/Linux

Uname -a for the ubuntu 12.04
Linux ubuntu1204 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

** Affects: xorg (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: bot-comment mouse precise scroll touchpad usb
-- 
scroll wheel doesn't work with VmarkerUSB
https://bugs.launchpad.net/bugs/996176
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xorg in Ubuntu.

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to     : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

Reply via email to