Maybe this can help you. I did some experiments on a Touch.
First I give you the fbset output as reference.
Code:
[root@(none) ~]# fbset
mode "800x600-0"
# D: 0.033 MHz, H: 0.034 kHz, V: 0.055 Hz
geometry 800 600 800 1280 16
timings 30000000 8 164 4 18 4 1
accel false
rgba 5/11,6/5,5/0,0/0
endmode
Now comes the reading of the touch coordinates:
Code:
[root@(none) ~]# result=`od -i -N 128 /dev/input/event1`; echo "$result"
// At this point I touched the top right corner of the screen (device held as usual). The coordinates are in the lines that start with 0000120 and 0000140, they are 41x40.
0000000 -12329 22021 -15044 4 3 0 549 0
0000020 -12329 22021 -15017 4 3 1 776 0
0000040 -12329 22021 -15007 4 3 24 0 0
0000060 -12329 22021 -14999 4 1 330 0 0
0000100 -12329 22021 -14992 4 0 0 0 0
0000120 -12314 22021 -5950 13 3 1 41 0
0000140 -12314 22021 -5922 13 3 0 40 0
0000160 -12314 22021 -5911 13 3 24 101 0
0000200
And a further example:
Code:
[root@(none) ~]# result=`od -i -N 128 /dev/input/event1`; echo "$result"
// At this point I touched the bottom left corner. The coordinates are in the lines that start with 0000120 and 0000140, they are 560x781.
// As you see the coordinates of the previous touch event are repeated in the lines that start with 0000020 and 0000040.
0000000 -12214 22021 15 15 3 0 41 0
0000020 -12214 22021 42 15 3 1 40 0
0000040 -12214 22021 53 15 3 24 0 0
0000060 -12214 22021 60 15 1 330 0 0
0000100 -12214 22021 66 15 0 0 0 0
0000120 -12207 22021 11228 5 3 1 560 0
0000140 -12207 22021 11259 5 3 0 781 0
0000160 -12207 22021 11270 5 3 24 100 0
0000200
So you could call in a script od -i -N 128 /dev/input/event1, and parse the result.