These programs do not work for me.
I assume they are for the ADS board, or something else.
what you can do to test your touchscreen:
cat /proc/bus/input/devices
locate here your event id
if you load the keyboard driver it will probably be event1 otherwise if you just have the touchscreen driver loaded
it should be event0
then you can do a quick and dirty test:
cat /dev/input/event[N]
then touch the screen.
if you see gibbly goop here, then it works.
control-c to kill it, type reset if it borked your console output.
now you can write some code to parse the input_event structure.
But, I have some other problems with the touchscreen.
I have a deadzone on the left side, the driver is filtering these events.
also I get inconsistent flesh press information.
when I use flesh of finger to press, I can get events upto 600 pixels away.
if I use rigid object, fingernail stylus I get more consistent press information.
but still some bad press data.
seems it is the driver doing it all.
|