From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Calibrating touch screen
Date: Mon, 25 Mar 2013 09:23:53 -0600 [thread overview]
Message-ID: <51506C09.9060503@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LZ2K0Q4CjrGojjSPwFB+RL6NAkFu5wvZG1s1yr-PD00Lg@mail.gmail.com>
On 2013-03-25 07:54, Burton, Ross wrote:
> On 25 March 2013 13:34, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> Ross: Any thoughts here? This isn't good coming up to release.
>
> xinput-calibrate is the answer, which is sadly in meta-oe still. This
> needs to be merged. Last time I looked at this there was on-going
> rewriting of it's startup, I'll see if that's integrated so we can
> migrate it.
>
> What hardware/touchscreen are you using?
Sadly it's proprietary and not public.
Basically OMAP4 (like a Panda) with LCD+touch.
For my case, I found that I could just adjust these things in
the Xorg.conf. I use this file as /etc/X11/xorg.conf.d/11-touchscreen.conf
Section "InputClass"
Identifier "ADS7846 Touchscreen"
MatchProduct "ADS7846 Touchscreen"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "SwapAxes" "false"
Option "InvertX" "false"
#Option "InvertY" "true"
Option "Calibration" "102 3768 3590 275"
EndSection
The calibration values came from xinput-calibrate which I imported for
just this project. As you say, that should get moved to OE-core.
The code in /etc/X11/Xsession.d/30xTs_Calibrate.sh seems totally
broken (and is how I came to my original question)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-03-25 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 13:15 Calibrating touch screen Gary Thomas
2013-03-25 13:34 ` Richard Purdie
2013-03-25 13:54 ` Burton, Ross
2013-03-25 15:23 ` Gary Thomas [this message]
2013-03-25 15:29 ` Burton, Ross
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=51506C09.9060503@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.