Tap anywhere on the screen to continue

Reference: http://www.arm9home.net/read.php? Tid = 3899

Keywords: mini2440 S3C2440 qtopia touch screen Calibration

This is the description of a buddy on the Internet:

I. porting process:
1. the system configuration file is slightly modified by the kernel's own s3c2410_defconfig;
2. Compile the s3c2410_ts.c, mini2440_adc.c and s3c24xx-adc.h files in the kernel 2.6.30.4 of the friendly CD;
3. In Kernel configuration, select the two modules and compare the input device section of the friendly 2.6.29 configuration file. No exception is found;
4. The file system is the QT image compiled on the CD.
Ii. symptom:
1. After loading the root user, the screen stops at the Green welcome image of QT., "Tap anywhere on the screen to continue ."
2. the touch screen does not respond.
3. The print information of kernel startup is displayed. Both the ADC and TS modules are loaded successfully.
ADC initialized
S3C2410 touchscreen successfully loaded
Input: S3C2410 touchscreen as/class/input/input0

4. Enter the command on the terminal: CAT/proc/bus/input/devices. The result is as follows:
I: Bus = 0013 vendor = dead Product = Beef version = 0101
N: Name = "S3C2410 touchscreen"
P: phys =
S: sysfs =/class/input/input0
U: uniq =
H: handlers = event0 evbug
B: EV = B
B: Key = 0
B: ABS = 1, 1000003

Iii. solution (software ):

In the root file system of the board, there is a QT Initialization Script qtopia under the/bin directory. Enter the following command on the terminal:
# Cat/bin/qtopia

[root@FriendlyARM /]# cat /bin/qtopia#!/bin/shexport TSLIB_TSDEVICE=/dev/input/event0export TSLIB_CONFFILE=/usr/local/etc/ts.confexport TSLIB_PLUGINDIR=/usr/local/lib/tsexport TSLIB_CALIBFILE=/etc/pointercalexport QTDIR=/opt/Qtopiaexport QPEDIR=/opt/Qtopiaexport PATH=$QTDIR/bin:$PATHexport LD_LIBRARY_PATH=$QTDIR/lib:/usr/local/lib:$LD_LIBRARY_PATHTS_INFO_FILE=/sys/devices/virtual/input/input0/ueventif [ -e $TS_INFO_FILE -a "/bin/grep -q TouchScreen < $TS_INFO_FILE" ]; then        export QWS_MOUSE_PROTO="TPanel:/dev/input/event0 USB:/dev/input/mice"        if [ -e /etc/pointercal -a ! -s /etc/pointercal ] ; then                rm /etc/pointercal        fielse        export QWS_MOUSE_PROTO="USB:/dev/input/mice"        >/etc/pointercalfiunset TS_INFO_FILEexport QWS_KEYBOARD=TTY:/dev/tty1export KDEDIR=/opt/kdeexport HOME=/rootexec $QPEDIR/bin/qpe 1>/dev/null 2>/dev/null

Ts_info_file =/sys/devices/virtual/input/input0/uevent
Uevent, that is, the user space event, is an event notification sent by the kernel to the user space, so that the application can have the opportunity to respond to the event to the file system to find this stuff...
# Cd/sys
# Find-name uevent
Failed to find/sys/devices/virtual/input/input0/uevent
However, the/sys/class/input/input0/uevent is found.
I don't know where the path/sys/class/input/input0/uevent is defined, so I only need to change the qtopia script in the root file system. modify ts_info_file =/sys/class/input/input0/uevent in the script
After modification, you can use the new file system ....

I thought this was the same reason. No one knows that the change is useless. Some people say that this change can be good (I am not familiar with qtopia, And I know something about Android). Finally, I found that we are not the same problem,

======================================================= ==========

4. My questions (SB ):

It's easy. The touch screen is broken, and it will be OK after a new welding.

We want to copy the hardware of the Development Board and split all the boards, including the screen and touch screen. We have dropped the screen line of the touch screen. Oolong and European Cup have not yet played "Oolong ".

2012 European Cup:

Poland Greece Russia Czech Republic
Netherlands Denmark Germany Portugal
Spain Italy Ireland Croatia
France 1:1 England Ukraine 2:1 Sweden