Dear Peter: I try the latest version later, thanks for all your reply. <img goomoji="360" style="margin: 0pt 0.2ex; vertical-align: middle;" src="cid:360@goomoji.gmail"> B.R Leo <div class="gmail_quote"> 2010/11/18 Peter Hutterer <<a href="mailto:peter.hutterer@who-t.net">peter.hutterer@who-t.net</a>> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On Thu, Nov 18, 2010 at 10:40:45AM +0800, Leo wrote: > >> My evdev version is xf86-input-evdev-2.4.99.901. > I still feel puzzled: > 1. But why XEV can not get the right position?I test XEV in my ubuntu10.04, > I can see the mouse's position changing. > How does xserver's event flows? e.g: kernel->dev/input/eventX -->read and > analyzed by evdev-->WM-->app ??? </div><a href="http://who-t.blogspot.com/2010/07/input-event-processing-in-x.html" target="_blank">http://who-t.blogspot.com/2010/07/input-event-processing-in-x.html</a> <div class="im"> > 2. I google the my question, they say if we support touchscreen, we'd > install tslib or evtouch, > I dont know what's relation between these component, Can evdev handle the > touch screen independently? > or it may depends on the other such as tslib or anything else... </div>evdev will handle touchscreens and as I said, I don't really see an unusual event stream. that indicates that there may be a bug in the driver, or at least in the version you're running there. Have you tried running the latest git version? <div class="im"> > 3. I can not access your blog, I dont know the information below meas what? > Does it tell me, evdev has been removed, it can not work, or still handle > the input events? > > > > [ 59.855] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device > > > > [ 59.856] (II) UnloadModule: "evdev" > > > > [ 59.856] (EE) PreInit returned NULL for "ADS7846 Touchscreen" \ > > 4. can you paste your article, send to me? I try a lot , but still can not > access. I very appreciate what you did! </div>the blog essentially says that you can ignore this warning, it's a misconfiguration that has no real effect. <div><div></div><div class="h5"> Cheers, Peter > 2010/11/18 Peter Hutterer <<a href="mailto:peter.hutterer@who-t.net">peter.hutterer@who-t.net</a>> > > > On Thu, Nov 18, 2010 at 09:28:47AM +0800, Leo wrote: > > > Dear Peter: > > > I attach my evtest&&xev log. it seems to work ok. > > > But there's something intersting, I just repeat operation on the > > different > > > place of touch screen. > > > Evtest can distinguish the position, you can have a look at the log, the > > ABS > > > coordinate keep changing, > > > While XEV I run on my device, this test seems not as what we want, it > > can > > > distinguish the BTN_PRESS && BTN_RELEASE or > > > motion, but the position never changed. > > > > what version of evdev are you running? have you tried git master and/or an > > older version of evdev? If it works, can you bisect to it, I don't see > > anything in the evtest stream that should make this device not work. > > > > > > > I guess there's some place to transform the event as user want in Xorg. > > > evtest may read from the /dev/input/event3 directly, it's ok. But XEV > > Which > > > may depends on X11's transformation, so appears the different situation. > > > > > > Please give some hints, thanks [?] > > > > > > BTW: I can not open the LINK [?] > > > > > <a href="http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html" target="_blank">http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html</a> > > > Is there any other website ? > > > > no, I just wrote this up today and it seems to work here. > > > > Cheers, > > Peter > > > > > 2010/11/18 Peter Hutterer <<a href="mailto:peter.hutterer@who-t.net">peter.hutterer@who-t.net</a>> > > > > > > > On Wed, Nov 17, 2010 at 09:34:49AM +0800, Leo wrote: > > > > > I prepare to port Meego(Linux based) to my devkit8000, follow the > > porting > > > > > guide > > > > > <a href="http://wiki.meego.com/ARM/Meego_on_B...d_from_scratch" target="_blank">http://wiki.meego.com/ARM/Meego_on_B...d_from_scratch</a>< > > > > <a href="http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch" target="_blank">http://wiki.meego.com/ARM/Meego_on_Beagleboard_from_scratch</a>> > > > > > everything seems ok: show the home screen, launch the application, > > > > > But there's problem about touch screen. Meego can not recognize my > > > > behavior. > > > > > I'm not sure it's related with Xorg or driver. Here is my Xorg log: > > > > > > > > > > 59.837] (II) config/udev: Adding input device ADS7846 Touchscreen > > > > (/dev/i) > > > > > [ 59.837] (**) ADS7846 Touchscreen: Applying InputClass "default" > > > > > [ 59.841] (**) ADS7846 Touchscreen: Applying InputClass "evdev > > > > touchscreen " > > > > > [ 59.842] (**) ADS7846 Touchscreen: always reports core events > > > > > [ 59.842] (**) ADS7846 Touchscreen: Device: "/dev/input/event3" > > > > > [ 59.842] (--) ADS7846 Touchscreen: Found absolute axes > > > > > [ 59.842] (--) ADS7846 Touchscreen: Found x and y absolute axes > > > > > [ 59.842] (--) ADS7846 Touchscreen: Found absolute touchscreen > > > > > [ 59.843] (II) ADS7846 Touchscreen: Configuring as touchscreen > > > > > [ 59.843] (**) ADS7846 Touchscreen: YAxisMapping: buttons 4 and 5 > > > > > [ 59.843] (**) ADS7846 Touchscreen: EmulateWheelButton: 4, > > > > EmulateWheelIner0 > > > > > [ 59.845] (II) XINPUT: Adding extended input device "ADS7846 > > Touchscreen" > > > > () > > > > > [ 59.851] (II) ADS7846 Touchscreen: initialized for absolute axes. > > > > > [ 59.854] (II) config/udev: Adding input device ADS7846 Touchscreen > > > > (/dev/i) > > > > > [ 59.854] (**) ADS7846 Touchscreen: Applying InputClass "default" > > > > > [ 59.855] (**) ADS7846 Touchscreen: always reports core events > > > > > [ 59.855] (**) ADS7846 Touchscreen: Device: "/dev/input/mouse0" > > > > > [ 59.855] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for > > device > > > > > [ 59.856] (II) UnloadModule: "evdev" > > > > > [ 59.856] (EE) PreInit returned NULL for "ADS7846 Touchscreen" > > > > > [ 60.102] (NI) OMAPFBSaveScreen: Dim backlight? > > > > > > > > > > who has the experience about these kind of problem, pls talk to me! > > > > > thanks very much > > > > > > > > does it work at all? do you see events come out of the device when you > > run > > > > evtest against it? > > > > > > > > as for the error message: > > > > > > <a href="http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html" target="_blank">http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html</a> > > > > > > > > Cheers, > > > > Peter > > > > > > > > > > > > </div></div></blockquote></div>