Re: Zaurus 860 native X and calibration
Nick Mitchell <[email protected]> Mon, 16 Aug 2004 08:02:48 -0700 (PDT)
| Newsgroups | gmane.linux.debian.devel.3com-pilot,gmane.linux.debian.devel.handheld |
|---|---|
| Message-ID | <[email protected]> |
howdy Klaus, thanks very much for the response! I have tried both the fbvnc and native X (in chroot) approaches. The touchscreen tracking problem was with the second, and I just now found the problem: not only do I need /etc/pointercal to be in the chroot, but also /etc/ts.conf and /usr/share/ts (the latter contains the touchscreen plugins). now the tracking in native chroot X works fine; i notice one of the modules included in /etc/ts.conf from pdaxrom is "tracking linear" :) i suppose that was the problem. native chroot X works great now (well, still have to work out the kinks with power management, like suspend on lid close) by the way, I'm not running the xserver-xfree86 framebuffer X, but rather just using the /usr/X11R6/bin/Xfbdev that pdaxrom ships with (it appears that this is from keith packard's version of X). thanks again, nick --- Klaus Weidner <[email protected]> wrote: > On Sun, Aug 15, 2004 at 05:53:05AM -0700, Nick > Mitchell wrote: > > Hello! Thanks very much to pocketworkstation for > the > > Debian chroot environment. It's working very well, > on > > top of a pdaXrom 1.0.5 base ROM. There's basically > two > > annoyances I haven't yet been able to figure out, > > both related to running a native X within the > chrooted > > environment. First, the touchscreen calibration is > > slightly off. Second, when I run it as a normal > user, > > the touchscreen, while it seems to accept input, > does > > so in an unreliable, jerky, manner. > > Have you tried running the Xf4vnc framebuffer server > together with the > fbvnc client for the local display? That's what I'm > using in the chroot > debian environment. I never tried native X11 on > current models, so I > can't comment on that. > > > On the second point: I don't think this works, > even in > > the native environment, but does anyone know why? > > This is strange, my guess would be that there's a > separate process that > also reads from the touchscreen and the resulting > race condition breaks > the protocol. > > Or does the native X use something other than the > default touchscreen > device interface to read that's timing sensitive? > Last time I looked > there was no source available for tha pdaXrom X > server unfortunately. > > -Klaus > _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com