Comment 129 for bug 549447

Let's kill this bug once and for all.

My eGalax touchscreen gets detected as a tablet, but basically works.

The catch is: Evdev detects four axes: Absolute X axis (always in coordinate 42), Absolute Y axis (always in coordinate 42), Absolute Z axis (registering motion flawlessly), and Rotary X axis (also registering motion flawlessly). The axes are swapped, guys.

[root@faeris faeris]# xinput list-props 11
Device 'eGalax INC. USB TouchController':
        Device Enabled (115): 1
        Device Accel Profile (237): 0
        Device Accel Constant Deceleration (238): 1.000000
        Device Accel Adaptive Deceleration (240): 1.000000
        Device Accel Velocity Scaling (241): 10.000000
        Evdev Axis Inversion (242): 0, 0
        Evdev Axis Calibration (243): 32, 0, 1000, 0
        Evdev Axes Swap (244): 0
        Axis Labels (245): "Abs X" (233), "Abs Y" (234), "Abs Z" (235), "Abs Rotary X" (236)
        Button Labels (246): "Button Left" (116), "Button Unknown" (232), "Button Right" (118), "Button Wheel Up" (119), "Button Wheel Down" (120)
        Evdev Middle Button Emulation (247): 2
        Evdev Middle Button Timeout (248): 50
        Evdev Wheel Emulation (249): 0
        Evdev Wheel Emulation Axes (250): 4, 5, 0, 0
        Evdev Wheel Emulation Inertia (251): 10
        Evdev Wheel Emulation Timeout (252): 200
        Evdev Wheel Emulation Button (253): 4
        Evdev Drag Lock Buttons (254): 0

When I run xinput test, Abs X and Abs Y are always at 42, but Abs Z and Abs Rotary X are registering accurately the motion. Also, the screen answers to clicks. What can I do to invert axes, so that X can move my pointer with Z and Rotary X (basically a workaround), or patching something so that Z and Rotary X come to be X and Y (the real fix)? This is also biting Ubuntu, so, I think it's upstream, and the evdev kernel driver is reading funky data from my touchscreen. This mail chain in the evdev list might be enlightening.

http://<email address hidden>/msg09730.html