>>>>> "Peter" == Peter Hutterer <peter.hutterer@xxxxxxxxxx> writes:
Hi,
Peter> it's a hack in userspace that works around wrong event
Peter> reporting. So yes, it works if you're using evtouch but if you
Peter> want to use any other driver that driver needs the same
Peter> hack. treating Z as X and RX as Y doesn't work too well for a
Peter> generic driver such as evdev, which has to deal with devices
Peter> where RX is a valid axis.
Hmm, I don't see it sending Z / RX:
sudo evtest /dev/input/event12
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x1926 product 0x1 version 0x100
Input device name: "Nextwindow Touchscreen"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 272 (LeftBtn)
Event code 273 (RightBtn)
Event code 274 (MiddleBtn)
Event type 3 (Absolute)
Event code 0 (X)
Value 0
Min 0
Max 32767
Event code 1 (Y)
Value 0
Min 0
Max 32767
Event type 4 (Misc)
Event code 4 (ScanCode)
Testing ... (interrupt to exit)
sudo nwtool -u -i
Version: 2.91
Serial: 233025
Model: 1900
HW capabilities: 0x40
Rightclick delay: 1000 ms
Doubleclick time: 200 ms
Report mode: 1
Drag threshold: 500
Buzzer time: 40 ms
Buzzer tone: 40
Calibration key: 4
Calibration presses: 3
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
