Andre,

I'm sure that your response lives in a FAQ somewhere, but thank you for taking the time to point me
in the right direction.
Not necessarily. You don't _need_ them.

use /opt/SDK/bin/directfb-config when building/linking applications
against DirectFB.
It will tell you which objects need to be linked into your app.
You will likely need imageprovider, font, system and input drivers (to
be specified as arguments to directfb-config).
I'm still not sure how to completely get rid of dependencies on directfbrc and fb.modes, but have found a compromise between the static linking via directfb-config and the --sysconfig directive to configure. Would prefer not needing them, but could not figure out how to "compile in" the video mode. I figure that config files are better than
command line parameters for a touch screen only device...

This allowed me to find a bug in my inputdriver that I believe has now been addressed. However, I still have an issue with mmap() down in systems/fbdev/fbdev.c. I put in some debug code and all of the options to mmap() look ok, mmap(NULL,960000,3,1,8,0).
I wrote a test app with FBIOGET_VSCREENINFO/FBIOGET_FSCREENINFO that
verified the 960000 value as it seemed rather high to me. My (truncated) output is:

(*) DirectFB/Core: Single Application Core. (2009-03-15 01:21)
(*) Direct/Thread: Started 'VT Switcher' (260) [CRITICAL OTHER/OTHER 0/0] <2093056>...
(!) DirectFB/FBDev: Could not mmap the framebuffer!
   --> Invalid argument
(!) DirectFB/Core: Could not initialize 'system_core' core!
   --> Initialization error!
dfb_imagetest.c <42>:
       (#) DirectFBError [DirectFBCreate (&dfb)]: Initialization error!

The mmap() call is indeed returning MAP_FAILED (-1). I'd also seen a residual '--> no such file or directory' when using D_PERROR() for some quick debugging. Thought it was a red-herring, but fell back to using fb.modes/directfbrc via --sysconfig just in case. No
change.

I'm at a loss as to what to try next. The only thing that hints at being suspicious is that the file descriptor for the device, /dev/fb, is 8. Seems a bit high, but figure that DirectFB must be
opening other devices/files prior to initializing /dev/fb.

Appreciate any pointers.

-fred
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

Reply via email to