On Fri, Nov 05, 2010 at 09:27:06AM +0000, Tom Yates wrote:
> On Wed, 3 Nov 2010, Leo Arias wrote:
> 
> > The upgrade I did on the weekend left my touchscreen unusable. I checked
> > the xorg.conf and switched tslib to evdev and now I can use it without
> > major issues.
> 
> i'm guessing this involves editing /etc/X11/xorg.conf, finding the section 
> that says:
> 
> Section "InputDevice"
>       Identifier      "Touchscreen"
>       Driver          "tslib"
>       Option          "Device"        "/dev/input/event1"
> EndSection
> 
> and changing it to:
> 
> Section "InputDevice"
>       Identifier      "Touchscreen"
>       Driver          "evdev"
>       Option          "Device"        "/dev/input/event1"
> EndSection
> 
> if so, this doesn't work for me (after several reboots, my touchscreen is 
> still not responding correctly, and touches are registered a semi-random 
> distance and direction from where they occur).  if not, and anyone can 
> shed any light on what blooper i've just pulled, i'd be grateful.

check if you see this:

SHR r...@gojama / $ opkg info kernel
Package: kernel
Version: 2.6.34.7-oe9+gitr9+e4182f3551f1b8e8f8bd07a2d68e49a0ec4cd04a-r0.6

SHR r...@gojama / $ cat /etc/pointercal.xinput
xinput set-int-prop "Touchscreen" "Evdev Axis Calibration" 32 107 918 911 98
xinput set-int-prop "Touchscreen" "Evdev Axes Swap" 8 1
SHR r...@gojama / $ cat /etc/pointercal
557 38667 -4654632 -51172 121 46965312 65536

SHR r...@gojama / $ ls -lah /boot/
drwxr-xr-x    2 root     root        4.0K Oct 31 22:52 .
drwxr-xr-x   17 root     root        4.0K Nov  1 14:40 ..
-rw-r--r--    1 root     root          24 Oct 21 15:09 append-GTA02
lrwxrwxrwx    1 root     root          15 Oct 31 22:52 uImage -> uImage-2.6.34.7
-rw-r--r--    1 root     root        1.8M Oct 31 20:38 uImage-2.6.34.7
lrwxrwxrwx    1 root     root           6 Oct 21 22:29 uImage-GTA02.bin -> 
uImage

SHR r...@gojama / $ uname -a
Linux gojama 2.6.34.7 #1 Mon Nov 1 15:51:04 CET 2010 armv4tl GNU/Linux

/boot/uImage link is not updated correctly during 2.6.32 -> 2.6.34
upgrade, because only last number in version is used as u-a priority (ie
2.6.34.7 -> 4, 2.6.32.25 -> 25)

-- 
Martin 'JaMa' Jansa     jabber: [email protected]
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user

Reply via email to