Surface Memory deallocation

I used DFB 1.6.1 . I create surface using dfb->CreateSurface with DSDESC_PREALLOCATED. When the memory allocated through dfb_surface_buffer_create via CreateSurface is released. I don't see this memory getting released after dfb->release(surface). Please advice. Is there a API to release the memory?

Newer GNU toolchain doesn't compile directFB examples as it should?

I've been trying to run directFB on Xilinx boards with Zynq-ARM processor. I've compiled the directFB with directFB-examples with the older Codesourcery compiler (arm-xilinx-linux-gnueabi toolchain; version 2011.09-50 of Xilinx SDK) and examples work flawlessly.

I've wanted to move to the newer compiler since the one I mentioned above is very old. When I compile directFB with newest compiler (2013.02 of Xilinx SDK) examples can't be started and "df_dok" example exits with this message:

No supported modes found in /etc/fb.modes

Hi, List
I am trying to run some directfb examples programs on ARM platform. The
directfb libraries and examples binaries are come from buildroot and
also built by builtroot. None of these examples can run with success,
they all reported the same error on my target machine: No supported
modes found in /etc/fb.modes.
I tried to dump my 'fbset' output the the /etc/fb.modes:
mode "800x480-535209"
# D: 250000.000 MHz, H: 283125.708 kHz, V: 535209.278 Hz
geometry 800 480 800 480 32
timings 4 19 37 10 26 27 13
accel false
rgba 8/16,8/8,8/0,0/0
endmode
But, the error still the same. I also tried to input some basic settings
in /etc/directfbrc, also got the same error.
On the other hand, my frame buffer device /etc/fb0 should be okay, since
I can run other graphic programs on it, such as fbv (a framebuffer
picture viwer).
What's the most possible reason to cause the error? I enclosed in the
email the whole 'strace' output when I run the example program, hope
someone can have a look into it.
Another relative question: why I saw that directfb trying to open
/dev/tty0? What does /dev/tty0 mean to frame buffer?
Thanks in advance.
--
I can't go back to yesterday - because I was a different person then

direct_trace_lookup_symbol_at() is returning NULL in DFB-1.6.3 in multi-app mode

I was successful in bringing up DFB-1.4.17 7 & DFB-1.5.3 with linux-fusion versions 8.7.0 & 8.10.4 respectively on Set Top Box platform.

Now I am bringing up DFB-1.6.3 in multi-app mode with linux-fusion-9.0.0 on the same platform.

While bringing up DFB-1.6.3,especially when master process is getting initialized, I found that the exported function Core_AsyncCall_Handler passed in as argument to fusion_call_init() .In this function fusion_call_init() the handler is being resolved using direct_trace_lookup_symbol_at().However I am observing that the direct_trace_lookup_symbol_at() is returning NULL.This is happening for both enable-debug & disable-debug variants for all the shared functions exported using fusion_call_init() & fusion_call_init3().Later when slave process initializing DFB its invoking shared functions via fusion message loop thread.Now it doesn't execute the shared functions.As a result all the fusionees are getting destroyed.

Hello to the list

Hello everybody!
I am new to this list, so first of all A VERY BIG HELLO TO EVERYBODY!
Now the little (for you experienced users of DirectFB) question:
* PREAMBLE *
I am trying to run DirectFB program in a windowed mode in X11, using my
Desktop running Linux Mint 13 - Debian.
I installed everything (from -dev packages to libs...) so I can compile
and run examples in a windowed mode over Xorg Desktop running MATE
Desktop (A successor of Gnome).
I created a directfbrc file as following:
system=x11
force-windowed
mode=800x480
scaled=800x480
and the every application seems to run fine, with a strange behaviour
when grabbing the mouse.
I clearly see two mouse arrows: one jumping aroud the application window
and another one is following my mouse movement.
I can say my cursor is giving the application the event, but it is very
annoying to see two (or even more) objects onto screen when I move the
mouse.
Any help, clue, or what ever to disable this "feature"?
The same problem occurs when I run Qt-Embedded DirectFB window mode
application with -qws option, so I can say it is a DirectFB issue and
not Qt issue.
Best regards
--
,,,
(o o)
======oOO==(_)==OOo======
Gianluca Renzi
R&D
phone: +39.0542.609120
fax: +39.0542.609212
.oooO Oooo.
======( )==( )=======
\ ( ) /
\_) (_/
===================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(".)_/¯
_______________________________________________
directfb-users mailing list
directfb-users <at> directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users