Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Neil MacMunn <neil@gumstix.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: tslib Issue
Date: Wed, 02 Feb 2011 13:33:42 -0800	[thread overview]
Message-ID: <4D49CDB6.1040604@gumstix.com> (raw)
In-Reply-To: <4D4994F6.3080102@gumstix.com>

After a few cycles of:

  # rm /etc/pointercal
  # shutdown -r now
  # stat /etc/pointercal

I found that pointercal is only accessed on the first restart after it 
has been modified/created.

The problem seems to be that Xorg is started before ts_calibrate runs 
for the first time. I found a fairly simple hack that seems to fix the 
problem.

  # cp /etc/X11/Xinit.d/89xTs_Calibrate /etc/rc5.d/S89xTs_Calibrate

Though this fails to address the situation where ts_calibrate is run and 
pointercal already exists - a manual reboot is still necessary for the 
new calibration to take effect. Does anyone know of a better, more 
permanent fix?


--
Neil

On 11-02-02 09:31 AM, Neil MacMunn wrote:
> I am seeing the same thing using the omap3-palmtop-image for Gumstix
> Overo. On first boot, /etc/X11/Xinit.d/89xTs_Calibrate doesn't find
> /etc/pointercal so it runs ts_calibrate. The calibration doesn't take
> effect until I reboot though - restarting gpe-dm doesn't solve the problem.
>
> I think that the library /usr/lib/ts/linear.so looks for /etc/pointercal
> and defaults to some preset values if the file doesn't exist. I thought
> that restarting gpe-dm would reload linear.so (which fuser suggests it
> does) but this doesn't solve the problem. It would appear that I am
> missing something...
>
> --
> Neil
>
>
> On 11-02-01 12:37 PM, openembedded@rkmorris.us wrote:
>> Hi,
>>
>> I have successfully build and then run several OE images on my target
>> hardware (h1940) - and have noticed an interesting oddity (bug?).
>>
>> If I run the opie-image for example, everything works just great.
>> However, if I run an X-based image (like, say x11-gpe-image) when the
>> GUI starts up tslib calibration is run ... but then basically thrown
>> away, as the driver for the touchscreen is set to evdev by default
>> (and the touchscreen isn't calibrated / does not work right). If I
>> manually build and install xf86-input-tslib, and then configure the
>> input as tslib (not evdev) - once I restart gpe-dm it works as expected!
>>
>> Is this supposed to be the case, or perhaps something not configured
>> quite right in the builds?
>>
>> Thanks!
>>
>> ... Russell
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




  reply	other threads:[~2011-02-02 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 20:37 tslib Issue openembedded
2011-02-02 17:31 ` Neil MacMunn
2011-02-02 21:33   ` Neil MacMunn [this message]
2011-02-12  0:16 ` Khem Raj
2011-02-13  2:50   ` [Openembedded-users] " Russell Morris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D49CDB6.1040604@gumstix.com \
    --to=neil@gumstix.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox