Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Handling different touchscreen calibration systems
Date: Thu, 13 May 2010 21:10:43 +0200	[thread overview]
Message-ID: <20100513191042.GN3370@jama> (raw)
In-Reply-To: <1273771027.8785.26.camel@gnutoo-desktop>

On Thu, May 13, 2010 at 07:17:07PM +0200, GNUtoo wrote:
> *om-gta02 has an evdev driver which requires to feed /sys nodes with
> some calibration data,the script used is an Xsession.d script that uses
> xinput-calibrator

To be a bit more exact:
om-gta02 in SHR is using calibration of kernel driver through /sys, just
because it was first working solution, then we added possibility to use
xinput-calibrator (but that's used from Xsession.d script only after user 
manually starts it once - on some units it's more precise after own
calibration than with precalibrated kernel driver - no idea why)

> I had the idea of making recipes for handling int scripts or Xsession.d
> scripts,and including them in XSERVER in the machine configuration but
> I'm not shure it's a good idea.

SHR moved from xserver-kdrive-common to xserver-common, but default
stayed kdriver in task-x11. Would be great if other distros using
xserver-kdrive-common decide to join xserver-common camp and make your
changes only in one.

BTW: biggest change for switch from kdrive was to check/fix Xsession
script to never kill shell which is using them. They were launched in
new shell in kdrive and exit call was ok, but with xserver-common they
are sourced to Xsession script and calling exit stops Xorg loading.

Cheers,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         



      reply	other threads:[~2010-05-13 19:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 17:17 Handling different touchscreen calibration systems GNUtoo
2010-05-13 19:10 ` Martin Jansa [this message]

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=20100513191042.GN3370@jama \
    --to=martin.jansa@gmail.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