From: "Eric Bénard" <eric@eukrea.com>
To: holger+oe@freyther.de
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: qt4-embedded & tslib
Date: Sun, 06 Sep 2009 19:16:14 +0200 [thread overview]
Message-ID: <4AA3EE5E.70409@eukrea.com> (raw)
In-Reply-To: <200909061703.48206.holger+oe@freyther.de>
Holger Hans Peter Freyther a écrit :
> On Sunday 06 September 2009 14:31:36 Eric Bénard wrote:
>> Without this, tslib loads properly the module_raw (input in my case) but
>> none of the module (pthres, linear & co) defined in ts.conf (despite the
>> fact ts_test & co are running fine).
>
> Please google for the QWS_MOUSE_PROTO environement variable... tslib support
> is built as a plugin and Qt needs to be instructed to load it.
>
of course, without this variable it's not loaded at all.
But even with this variable, it doesn't work for me with
-plugin-mouse-tslib but works with -qt-mouse-tslib.
I tried :
tslib:/dev/input/event0 & tslib:/dev/input/touchscreen0
In fact, the module_raw (input) is properly loaded (which means QT was
instructed by QWS_MOUSE_PROTO to use tslib and TSLIB_PLUGINDIR is
properly set) but the other modules (pthres, linear & co) are not
properly loaded (from what I saw with strace they are found, opened, and
closed). If I comment out all the modules (not module_raw) from ts.conf
everything is properly loaded but of course tslib gives raw values to QT
so touchscreen is unusable.
Eric
next prev parent reply other threads:[~2009-09-06 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 12:31 qt4-embedded & tslib Eric Bénard
2009-09-06 15:03 ` Holger Hans Peter Freyther
2009-09-06 17:16 ` Eric Bénard [this message]
2009-09-06 22:22 ` Matthew Dombroski
2009-09-09 6:49 ` Eric Bénard
2009-09-09 22:02 ` Matthew Dombroski
2009-09-10 2:12 ` Holger Hans Peter Freyther
2009-09-10 3:19 ` Matthew Dombroski
2009-09-10 6:28 ` Eric Bénard
2009-09-24 19:02 ` [PATCH] " Eric Bénard
2009-09-25 11:29 ` Holger Hans Peter Freyther
2009-09-25 12:06 ` Eric Bénard
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=4AA3EE5E.70409@eukrea.com \
--to=eric@eukrea.com \
--cc=holger+oe@freyther.de \
--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