That's tricky to get round.
"preallocated" means that the CPU has obtained the buffer from somewhere
else, via a e.g. a malloc(). If you want the GPU to have access to this,
you need to do e.g. DMA on every access, or cache it in a pool.
Solution: don't do this, restrict yourself to CPU preallocated.
Note that this can be solved inside DirectFB by offering a back-up
scenario, but this will have a performance implication nonetheless.
hth
Niels
Matteo Fortini wrote:
I built qte 4.5.1 on a powerpc with the directfb driver.
I'm using the latest directfb 1.4 with a custom gfxdriver (Fujitsu
MB8629x + FBDev).
When I launch the qt demos, like
deform -qws -display directfb
I get
(!) Core/SurfBuffer: Buffer allocation failed!
--> Not supported!
Activating debug output, it seems that the negotiation for a private
preallocated buffer failed.
the buffer allocation fails when QTe tries to use a:
* preallocated buffer
* for GPU use
I don't know how GPU buffers should work, but I've seen that some
drivers add a GPU preallocated buffer pool. This is not used by
default on fbdev, however.
How can I fix it?
Thanks
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
--
.------------------------------------------.
| 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
