Hi,
On Tue, 2011-12-13 at 10:15 -0800, Ezequiel García wrote: > Thanks for all your answers. The picture is slowly starting > to become clearer to me. Good :-) > --- El lun 12-dic-11, Andre DRASZIK <[email protected]> escribió: > > decodes. That can only work with large enough video > > memory. > > > > Is this fb device memory allocated as kernel memory (like kmalloc and > friends)? > (I searched through my system fb device code but wasn't so easy to follow.) No. I assume you're working in a STAPI context where I think this is called AVMem. Via kmalloc() it is not possible to allocate large chunks of physically contiguous memory, which is needed for hardware acceleration. > Is this fb device memory *only* for DirectFB usage? Any applications using the frambuffer could use it, so I guess in reality only DirectFB. > So in this case I should tune the memory parameter as much as I can, > because when I insmod the device and assign it 40 Mb (20 Mb for each of two > devices) I am reserving those 40 Mb for lifetime, even if I use less. Yes, this will basically be used as texture memory, e.g. in WebKit. > Moreover, I should be very interested in trying to use only *one* > fb device instead of two, since that would mean half memory usage. Yes, makes sense if you only use one output... Cheers, Andre' _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
