Thank you ，I have tried it but it still didn‘t work。
what do you mean by saying “fix the driver in the kernel”？
My driver seems ok，here are the bootup message：
Loaded s3c-udc version Dec 2 2009 (DMA Mode)
input: s3c-keypad as /devices/platform/s3c-keypad/input/input0
s3c-keypad Initialized
S3C Keypad Driver
S3C Touchscreen driver, (c) 2008 Samsung Electronics
S3C TouchScreen got loaded successfully : 12 bits
input: S3C TouchScreen as /devices/virtual/input/input1
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
BTW, I have built tslib，I can use ts_calibrate to calibrate it,and I
can draw and drag using ts_test
thanks
--Weber
On Dec 2, 10:01 pm, "?? ?" <tonypopso...@gmail.com> wrote:
> hi,weber
> I got the same problem as you. It was some thing wrong with your screen
> driver.
> Maybe in your Framebuffer driver.
> Find the PowerManagerService.java
> modify the following function.
> boolean screenIsOn() {
> synchronized (mLocks) {
> return true;
> // return (mPowerState & SCREEN_ON_BIT) != 0;
> }
> }
>
> try it :-) and don't forget to fix the driver in the kernel.
> 2009/12/2 Michael Trimarchi <trimar...@gandalf.sssup.it>
>
> > Weber wrote:
> > > Hi,guys
> > > I have ported android 2.6.25 to my s3c smdk6410,and the filesystem is
> > > donut that I built from the source code.Now I can boot it up and see
> > > the main window.But when touching the item ,it does not have any
> > > response at all.
>
> > > My touchscreen driver src file is s3c_ts.c.
>
> > > I built tslib and calibrated it without android running,generating a
> > > pointercal file.But it still didn't work.
>
> > > Here are my debug info:
> > > # logcat *:E
> > > E/MountListener( 527): Failed to connect to vold
> > > E/MountListener( 527): java.lang.IllegalStateException
> > > E/MountListener( 527): at
> > > com.android.server.MountListener.listenToSocket(MountListener.java:
> > > 254)
> > > E/MountListener( 527): at com.android.server.MountListener.run
> > > (MountListener.java:274)
> > > E/MountListener( 527): at java.lang.Thread.run(Thread.java:
> > > 1060)
> > > E/MountListener( 527): Failed to connect to vold
>
> > Sorry but this is unrelated to the touchscreen problem :)
> > Michael
> > > # ls /dev/input
> > > event0 event1 ts0
> > > # cat /proc/bus/input/devices
> > > I: Bus=0019 Vendor=0001 Product=0001 Version=0001
> > > N: Name="s3c-keypad"
> > > P: Phys=s3c-keypad/input0
> > > S: Sysfs=/devices/platform/s3c-keypad/input/input0
> > > U: Uniq=
> > > H: Handlers=kbd event0
> > > B: EV=100003
> > > B: KEY=1fffe
>
> > > I: Bus=0013 Vendor=dead Product=beef Version=0101
> > > N: Name="S3C TouchScreen"
> > > P: Phys=input(ts)
> > > S: Sysfs=/devices/virtual/input/input1
> > > U: Uniq=
> > > H: Handlers=event1 ts0
> > > B: EV=b
> > > B: KEY=20 0 0 0 0 0 0 0 0 0 0
> > > B: ABS=1000003
>
> > > # cat /proc/bus/input/handlers
> > > N: Number=0 Name=kbd
> > > N: Number=1 Name=evdev Minor=64
> > > N: Number=2 Name=tsdev Minor=128
>
> > > What is the difference btw event1 and ts0?
>
> > > and my env for tslib are:
> > > export TSLIB_TSEVENTTYPE INPUT
> > > export TSLIB_CONSOLEDEVICE none
> > > export TSLIB_FBDEVICE /dev/graphics/fb0
> > > export TSLIB_TSDEVICE /dev/input/event1 //I had tried ts0,still the
> > > same
> > > export TSLIB_CALIBFILE /system/etc/pointercal
> > > export TSLIB_CONFFILE /system/etc/tslib/ts.conf
> > > export TSLIB_PLUGINDIR /system/lib/ts
>
> > > # getevent
> > > tsdev (compaq touchscreen emulation) is scheduled for removal.
> > > See Documentation/feature-removal-schedule.txt for details.
> > > could not get driver version for /dev/input/ts0, Invalid argument
> > > add device 1: /dev/input/event1
> > > name: "S3C TouchScreen"
> > > add device 2: /dev/input/event0
> > > name: "s3c-keypad"
> > > /dev/input/event1: 0000 0000 00000000
> > > /dev/input/event1: 0003 0000 00000505
> > > /dev/input/event1: 0003 0001 00000870
> > > /dev/input/event1: 0003 0018 00000001
> > > /dev/input/event1: 0000 0000 00000000
> > > /dev/input/event1: 0003 0000 00000506
> > > /dev/input/event1: 0003 0001 00000879
> > > /dev/input/event1: 0000 0000 00000000
> > > /dev/input/event1: 0003 0018 00000000
> > > /dev/input/event1: 0000 0000 00000000
> > > /dev/input/event1: 0003 0000 000006b6
>
> > > and then I open the DEBUG in s3c_ts.c,when touching it,the console
> > > prints:
> > > # D
> > > D
> > > D
> > > T: 853507, X: 28791, Y: 31853
> > > T: 878508, X: 28404, Y: 32080
> > > D
> > > T: 603508, X: 31842, Y: 18032
> > > T: 628524, X: 31689, Y: 18009
> > > D
> > > T: 818507, X: 44988, Y: 16935
> > > T: 843508, X: 44818, Y: 17687
> > > T: 868506, X: 45122, Y: 17618
> > > T: 893508, X: 45248, Y: 18344
> > > D
> > > T: 648508, X: 45725, Y: 43406
> > > T: 673508, X: 45500, Y: 43828
> > > D
> > > T: 478507, X: 24101, Y: 19161
> > > T: 503508, X: 23650, Y: 19044
> > > T: 528508, X: 23943, Y: 18982
> > > It seems that android didn't get my input coordinate but the kernel
> > > did
>
> > > and the post
>
> >http://groups.google.com/group/android-porting/browse_thread/thread/f...
> > > says that " Power Management support "is necessary ,so I chose it
> > > and rebuilt ,but it still has no response .
>
> > > so could anyone tell me what are my problems ?and How should i do to
> > > make the touchscreen work?
> > > Thanks!
> > > ---Weber
>
> > --
> > unsubscribe:
> > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
> > website:http://groups.google.com/group/android-porting
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
