Well, this mouse sends out 0x00 instead of 0xFF when a negative X-Axis movement is performed. And does also report 0x00 instead of 0xFF when a positive Y-Axis movement does occur. A normal PS/2 mouse is using the range 0xFF to 0x80 or 0x00 (?) to report negative X-Axis movements. But the Labtec 4D+ mouse uses the oposite range: 0x00 to 0xFF (where (X-Axis) 0x00 means a movement of -1, and 0x01 means -2, ...). The values are also reversed on positive Y-Axis movement. Labtec 4D+ PS/2 mouse: X-Axis positive: 0x00 to 0xFF or 0x7F (?) (0x00 = +1 or 0, not sure) X-Axis negative:0x00 to 0xFF (?) (0x00 = -1) Y-Axis positive: 0x00 to 0xFF (?) (0x00 = +1 or 0) Y-Axis negative: 0x00 to 0xFF (?) (0x00 = -1) A normal PS/2 mouse: X-Axis positive: 0x00 to 0xFF (?) (0x00 = +1 or 0) X-Axis negative: 0xFF to 0x00 or 0x80 (?) (0xFF = -1) Y-Axis positive: 0xFF to 0x00 (?) (0xFF = +1) Y-Axis negative: 0x00 to 0xFF (?) (0x00 = +1) Well, that was what I was able to read out of the debugging output from moused. As you can see, I'm not completely sure about all the max and minimum values. The Labtec mouse worked after applying this patch: http://www.leakingmemory.org/moused_05_08_2003/moused.c.patch and starting moused manually: # moused -t ps/2Received on Fri May 09 2003 - 07:10:26 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:07 UTC