Error with the tslib

Hi there!

I compiled a new system for mini2440 using Buildroot (I'm trying to use
Qt). I used the kernel avaliable here in this site (2.6.32.2) and compiled
it and the libs Ok. The screen is working (is a X35), and the system runs
Ok. But, when I try to run a ts app (e.g. ts_calibrate), it returns
'ts_open: No such device'. The environment variables that I set are the
following:

export TSLIB_TSEVENTTYPE=INPUT
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event1
export TSLIB_CALIBFILE=/etc/pointercal
export QWS_MOUSE_PROTO=tslib:/dev/input/event1

I tried to change the 'event' with 0, 2 and 3, but the error is the same.
Anyone can help me?

You can check that your TSLIB_DEVICE is really event1 by:

cat /dev/input/event1 and moving the stylus around on the screen while
logged in using minicom or similar.  You should see garage on the minicom
screen.

Did you cross-compile your own tslib?  I'd check that it really has been
cross-compiled.

Also, maybe have a look at:
http://billforums.station51.net/viewtopic.php?f=8&t=15&start=130

Good luck!
Dave

Hello!

First, I can't open any of /dev/input/eventX. When I try to open it with
cat, it return:

cat: can't open '/dev/input/eventX': No such device

About the cross-compilation, I compiled it with the Buildroot tool - it
generated a complete system, with the selected libraries. I selected Qt ->
Mouse support -> tslib.

I also tried to run ts_finddev, but it returns nothing.

What entries do you have in /dev/input?

There is also a place to look in /sys.

Sorry, I am at work and the full path is at home.

Something like /sys/proc/virtual/ .. ??

Try looking in:

/sys/devices/virtual/input/input1

and seeing what is there and then:

cat /sys/devices/virtual/input/input1/eventX and so forth.

For event1 you might see something like:
c 13:65 

then the /dev/input entry for event1 should have the same:
c 13:65

I have only observed this and have not tried playing around with these
entries.  I believe mdev or udev creates them.

In the /dev/input, I have the following:

event0 event1 event2 event3 mice mouse0 mouse1 mouse2 mouse3

In the /sys/devices/virtual/input, I only have a folder called 'mice'.

Rafael,

are you using persistent device nodes? Or do you run 'udev' on your system?
If you are using persistent device nodes there is no correlation between
the device nodes and the really existing devices in your kernel.

Ups, comment forgotten: When your /sys/devices/virtual/input is mostly
empty, it means:
a) there is no touchscreen device registered
b) the touchscreen driver in the kernel is disabled (or not loaded in the
case of a module)

A solution for a) needs a kernel patch, a solution for b) needs some
changes in the kernel configuration

Sorry, but I don't know what you said means...

Solved. The Touchscreeen modulo weren't enabled in the Kernel config.

here i am using capacitive touchscreen .
i am not able to move the touch point on lcd .

please suggest me where i am going wrong.

#dmesg 

input: TSC2007 Touchscreen as /devices/virtual/input/input1

#cat /proc/bus/input/devices 
I: Bus=0019 Vendor=0001 Product=0001 Version=0003
N: Name="TWL4030 Keypad"
P: Phys=twl4030_keypad/input0
S:
Sysfs=/devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypad/input/input0
U: Uniq=
H: Handlers=kbd event0 evbug 
B: EV=100013
B: KEY=400 0 0 0 0 0 0 0 0 0 80000000 0 800 8400 0 c011 13d08bfe
B: MSC=10

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="TSC2007 Touchscreen"
P: Phys=3-005c/input0
S: Sysfs=/devices/virtual/input/input1
U: Uniq=
H: Handlers=mouse0 event1 evbug 
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=1000003

I: Bus=0003 Vendor=192f Product=0416 Version=0111
N: Name="USB Optical Mouse"
P: Phys=usb-ehci-omap.0-2.4/input0
S:
Sysfs=/devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.0/input/input2
U: Uniq=
H: Handlers=mouse1 event2 evbug 
B: EV=17
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=143
B: MSC=10

using 
#evtest /dev/input/event1 
home/root/evtest /dev/input/event1
Input driver version is 1.0.0[ 1152.566101] evdev.c(EVIOCGBIT): Suspicious
buffer size 511, limiting output to 64 bytes. See
http://userweb.kernel.org/~dtor/eviocgbitl

Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "TSC2007 Touchscreen"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 330 (Touch)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value      0
      Min        0
      Max      320
      Fuzz       4
      Flat       8
    Event code 1 (Y)
      Value      0
      Min        0
      Max      480
      Fuzz       4
      Flat       8
    Event code 24 (Pressure)
      Value      0
      Min        0
      Max      255
Testing ... (interrupt to exit)

Event: time 1129.296752, type 3 
(Absolute), code 0 (X), value 89
Event: time 1129.298858, type 3 (Absolute), code 1 (Y), value 384
Event: time 1129.299011, 
------------ Report Sync -------
Event: time 1129.321746, type 3 (Absolute), code 0 (X), value 0
Event: time 1129.321990, type 3 (Absolute), code 1 (Y), value 0
Event: time 1129.322113, -------------- Report Sync ------------

Event: time 1129.372467, type 3
(Absolute), code 0 (X), value 89
Event: time 1129.372833, type 3 (Absolute), code 1 (Y), value 384
Event: time 1129.372955, -------------- Report Sync ------------

Event: time 1130.796813, type 3 
(Absolute), code 0 (X), value 168
Event: time 1130.798919, -------------- Report Sync ------------

Event: time 1130.817749, type 3 (Absolute), code 0 (X), value 0
Event: time 1130.817993, type 3 (Absolute), code 1 (Y), value 0
Event: time 1130.818115, -------------- Report Sync ------------

Event: time 1130.890594, type 3
(Absolute), code 0 (X), value 168
Event: time 1130.892639, type 3 (Absolute), code 1 (Y), value 384
Event: time 1130.892822, -------------- Report Sync ------------