Hi, Chris...
I have tried a similar procedure, when building DirectFB 1.1.1 with tslib
1.0, for architecture Atmel AVR32. I get the following:
[EMAIL PROTECTED] /]# avr32-linux-dfbinfo
=======================| DirectFB 1.1.1 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2008-05-29 05:41)
(*) Direct/Thread: Started 'VT Switcher' (501) [CRITICAL OTHER/OTHER 0/0]
<2093056>...
avr32-linavr32-linux-dfb[495]: segfault at 00000004 pc 2ac3601a sp 7f892208
ecr 28
ux-dfbinfo: can't resolve syavr32-linux-dfb[495]: segfault at 00000010 pc
2aaf1414 sp 7f89201c ecr 24
mbol 'tslib_parse_vars'
(!) [ 495: 0.000] --> Caught signal 11 (at 0x4, invalid address) <--
Segmentation fault
As with others, ts_calibrate and ts_test work just fine.
I have built 1.1.1 without tslib support, and the DirectFB demos work just
fine (but of course no input device).
Any thoughts?
Thanks,
Peter
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of cdaviduik
> Sent: Friday, September 05, 2008 7:48 AM
> To: directfb-users@directfb.org
> Subject: Re: [directfb-users] Specifying tslib for DirectFB
> touchscreen input driver
>
>
> Hello,
> Assuming you are using Bitbake first make a copy of the
> directfb directory located in
> gumstix-oe\com.gumstix.collection\packages and move it to
> user.collection\packages\directfb. Then configure directfb
> for use with tslib by editing your directfb_1.1.x.bb file so
> EXTRA_OECONF looks something similar to this:
>
> EXTRA_OECONF = " \
> --with-gfxdrivers=none \
> --with-inputdrivers=tslib \
> --enable-libmpeg3=no \
> --enable-freetype=yes \
> --enable-sdl=no \
> --enable-vnc=no \
> --enable-fbdev \
> --disable-x11 \
> TSLIB_CFLAGS=\"-I${INSTALL_PATH}/include\" \
> TSLIB_LIBS=\"-L${INSTALL_PATH}/lib\" \
> "
> Once everything is compiled and running on your gumstix you
> will have to export the following variables:
>
> export TSLIB_TSDEVICE=/dev/input/touchscreen0
> export TSLIB_CONFFILE=/etc/ts.conf
> export TSLIB_PLUGINDIR=/usr/lib/ts
> export TSLIB_CALIBFILE=/etc/pointercal
>
> and make a symbolic link to you touchscreen in /dev/input:
>
> ln -s event0 tslib0
>
> Depending on your touchscreen device name some of these
> values may be slightly different however once you get all of
> this setup hopefully things will start working out for you.
> Good luck
>
>
> I'm seeing exactly the same behaviour and have the same
> config. Did you find a solution or an alternative?
> Darren
>
>
> cdaviduik wrote:
> >
> > I just wanted to make a small correction to my last post.
> It appears
> > when I specify --with-inputdrivers=tslib and then rebuild
> and reload
> > my file system directfb does not utilize any input drivers
> (typically
> > these appear after the 'VT Switcher' line):
> >
> > =======================| DirectFB 1.1.0
> |=======================
> > (c) 2001-2007 The DirectFB Organization (directfb.org)
> > (c) 2000-2004 Convergence (integrated media) GmbH
> > ------------------------------------------------------------
> >
> > (*) DirectFB/Core: Single Application Core. (2008-06-04 20:06)
> > (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 1358)...
> > (!) Direct/Modules: Could not open module directory
> > `/usr/lib/directfb-1.1-0/gfxdrivers'!
> > --> No such file or directory
> > (*) DirectFB/Graphics: Generic Software Rasterizer 0.6
> (directfb.org)
> > (*) DirectFB/Core/WM: Default 0.3 (directfb.org)
> > (*) FBDev/Mode: Testing 480x272 RGB16
> > (*) FBDev/Mode: Preparing switch to 480x272 RGB16
> > (*) FBDev/Mode: Testing 480x272 RGB16
> > (*) FBDev/Mode: Preparing switch to 480x272 RGB16
> > (*) FBDev/Mode: Testing 480x272 RGB16
> > (*) FBDev/Mode: Preparing switch to 480x272 RGB16
> > (*) FBDev/Mode: Testing 480x272 RGB16
> > (*) FBDev/Mode: Preparing switch to 480x272 RGB16
> > (*) FBDev/Mode: Testing 480x272 RGB16
> > (*) FBDev/Mode: Preparing switch to 480x272 RGB16
> > (*) FBDev/Mode: Switched to 480x272 (480x272) at 16 bit
> RGB16 (wanted
> > RGB16).
> > ...
> >
> > When I touch the screen to generate input, no events occur.
> If I try
> > running ts_calibrate/ts_test they work fine. Somehow I just need
> > directfb to use tslib.
> >
> > Are there any steps I am missing??? Anything else I can try???
> > From what I understand, getting directfb running with tslib
> should not
> > typically be such an arduous process.
> >
> > Thank you very much for any help.
> >
> > ______________________________
> >
>
> --
> View this message in context:
> http://www.nabble.com/Specifying-tslib-for-DirectFB-touchscree
> n-input-driver-tp17327192p19221341.html
> Sent from the DirectFB Users mailing list archive at Nabble.com.
>
> _______________________________________________
> directfb-users mailing list
> directfb-users@directfb.org
> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
>
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
