View previous topic :: View next topic |
Author |
Message |
ddc Guru

Joined: 29 Aug 2006 Posts: 521
|
Posted: Fri Jan 08, 2010 4:28 pm Post subject: Touchscreen |
|
|
hi
any guide about how (and what emerge) calibrate a Touchscreen ?
i'd like not to use HAL (cause the target is embedded, like Neo openmoko)
any help/guide ? |
|
Back to top |
|
 |
roarinelk Guru


Joined: 04 Mar 2004 Posts: 520
|
Posted: Sat Jan 09, 2010 7:21 pm Post subject: |
|
|
You can either use "tslib" (for Qt embedded, ...), or with a new enough X, the evdev
driver also supports touchscreens as long as they are supported by the kernel and
exported as "event" devices; then you need to play around with the calibration with
the xinput tool. |
|
Back to top |
|
 |
ddc Guru

Joined: 29 Aug 2006 Posts: 521
|
Posted: Tue Jan 12, 2010 5:49 pm Post subject: |
|
|
roarinelk wrote: | You can either use "tslib" (for Qt embedded, ...), or with a new enough X, the evdev
driver also supports touchscreens as long as they are supported by the kernel and
exported as "event" devices; then you need to play around with the calibration with
the xinput tool. |
thk U
about QT, is it possible to emerge it ? if so, which is the ebuild name ? i can't find in portage |
|
Back to top |
|
 |
roarinelk Guru


Joined: 04 Mar 2004 Posts: 520
|
Posted: Thu Jan 14, 2010 8:12 am Post subject: |
|
|
ddc wrote: | roarinelk wrote: | You can either use "tslib" (for Qt embedded, ...), or with a new enough X, the evdev
driver also supports touchscreens as long as they are supported by the kernel and
exported as "event" devices; then you need to play around with the calibration with
the xinput tool. |
thk U
about QT, is it possible to emerge it ? if so, which is the ebuild name ? i can't find in portage |
No ebuild; just unpack the qt-everywhere-* source tarball, adjust the incdir/libdirs
in mkspecs/qws/<your-toolchain>/qmake.conf to point to where you stored
your ARM libs and headers, adjust your toolchain if necessary and then cross-build it.
The configure script is a bit picky about what you enable;
you also might need to play a bit with the libdir/incdir paths until qmake correctly picks
up and links all external libraries you have enabled...
You could emerge the "standard" x11-based Qt ebuilds too, it just takes a _long_ time
to build and you need X; qt-embedded can use a framebuffer or EGL/openvg if you have
a capable cpu. |
|
Back to top |
|
 |
|