Peter Kemmer wrote:
> Hello All,
> i have a (hopefully) simple question: i just want to produce two 
> scenarios 1. no gfx-memory allocation happens at CPU-RAM  / 2. no 
> gfx-memory allocation happens at garphics controller RAM.
> Is there any easy way to force this ? I use devmem system for my 
> development setup, implemented the respective Layer and Surface-Pool. 
> How can i be sure, that not even a Image-Provider will use CPU's ram, 
> but always uses graphics-memory of the controller (its an experimental 
> FPGA ;-) with SDRAM interface).

There's no global setting for all surfaces. In the application you can always
use DSCAPS_SYSTEMONLY (CPU) or DSCAPS_VIDEOONLY (GPU) in surface or window
descriptions.

For window surfaces with none of the surface caps mentioned above, there's
the window-surface-policy option as mentioned in the other reply.

Using the desktop-buffer-mode option will allow you to force certain modes
for the layer surface in windowed mode, but unless you support multiple regions
per layer in hardware, you cannot use the "window" buffer mode which is quite
uncommon anyhow and has limitations on most hardware supporting it.

A global way to force allocation in your pool might be setting the priority
to ULTIMATE.

-- 
Best regards,
   Denis Oliver Kropp

.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/                 |
"------------------------------------------"


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

Reply via email to