Is it possible to use an usbtouchscreen under xvesa or
some workaround possible ( XTestFakeMotionEvent, /dev/input/eventx, gpm repeater mode)?
If I start a clean tinycore and connect my USB touchscreen it does work (exept for calibration)
and /dev/input/event6 is created.
Is this some generic driver in the kernel?
Then were is usbtouchscreen.ko for (which if I thought creates this input event)?
I installed and run evtest and get the following output
evtest /dev/input/event6
<snip>
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x4e7 product 0x8 version 0x100
Input device name: "Elo TouchSystems, Inc. Elo TouchSystems AccuTouch 3000U"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 272 (LeftBtn)
Event type 3 (Absolute)
Event code 0 (X)
Value 2719
Min 184
Max 3932
Event code 1 (Y)
Value 2571
Min 184
Max 3932
Event code 40 (Misc)
Value 0
Min 0
Max 256
Event type 4 (Misc)
Event code 4 (ScanCode)
Testing ... (interrupt to exit)
Event: time 1302169762.098830, type 3 (Absolute), code 0 (X), value 3032
Event: time 1302169762.098842, type 3 (Absolute), code 1 (Y), value 898
Event: time 1302169762.098844, type 3 (Absolute), code 40 (Misc), value 255
Event: time 1302169762.098858, -------------- Report Sync ------------
Event: time 1302169762.111334, type 4 (Misc), code 4 (ScanCode), value 90001
Event: time 1302169762.111351, type 1 (Key), code 272 (LeftBtn), value 1
Event: time 1302169762.111355, type 3 (Absolute), code 0 (X), value 3031
</snip>
To get it working with calibration would the folowing work:
I write a program which reads the /dev/input/event6 and translates it (calibrate)
- into XTestFakeMotionEvent() or
- into a new created /dev/input/event7
or does this give a conflict (multiple pointer movement)?
Welcome
FAQ
Downloads
Wiki
