From: Dirk Behme <dirk.behme@googlemail.com>
To: Birger Kroon <Birger.Kroon@sys.teleca.se>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OMAP 5912OSK and touchscreen under Qt/Embedded
Date: Tue, 13 Jun 2006 16:48:11 +0200 [thread overview]
Message-ID: <448ED02B.1060209@gmail.com> (raw)
In-Reply-To: <CA21EAA4DF189C40A3BC30A5A75DA56001D4C846@ratatosk>
Birger Kroon wrote:
> Does anyone here have experience of getting a touchscreen working with Qt/embedded?
>
> * I'm currently using the OMAP 5912OSK with the Mistral LCD unit.
> * I've got Qt/Embedded up and running on the platform (at least the display).
> * I'm using the latest kernel/patch.
> * I see events when I touch the screen so the low level drivers does work correct I beleive.
>
> My problem is that I do not know how to connect Qt/E with the touch screen drivers in the correct way. I've testet to set the 'QWS_MOUSE_PROTO' environment variable to different thing, but w/o success.
>
> - Do I need the tslib to use a TS under Qt/E?
Yes, you should use tslib for QT/E. Do calibration first
with tslib and then start QT/E.
Note that OMAP5912 touchscreen is broken in recent git. If
you use recent git, you should apply
http://linux.omap.com/pipermail/linux-omap-open-source/2006-June/007358.html
as well.
However, latest patch on http://www.muru.com/linux/omap/
should be okay (?).
Try to use -tslib to configure QT/E . If I remember
correctly there is a macro QT_QWS_TSLIB available within QT/E.
Maybe ask google as well.
Hth,
dirk
next prev parent reply other threads:[~2006-06-13 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:05 OMAP 5912OSK and touchscreen under Qt/Embedded Birger Kroon
2006-06-13 14:48 ` Dirk Behme [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-13 15:14 Birger Kroon
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=448ED02B.1060209@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=Birger.Kroon@sys.teleca.se \
--cc=linux-omap-open-source@linux.omap.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.