I just realized a behavior change in our new DFB 1.2 based systems driver as 
compared to our previous 1.0 based driver...

Newly created visible and non-visible surfaces do not appear to be cleared 
after they are allocated (previously done by default window stack I believe).

Is it an expectation of a CoreSurfaceBuffer Pool Manager to clear newly 
allocated raw pixel buffers?

>From what I can determine, it is-- at least for external (CSTF_EXTERNAL) 
>surfaces used for DSCAPS_VIDEOONLY surfaces (visible/non-visible).  Maybe 
>however it is not necessary for video low/high because the initial system 
>memory based surface is cleared by the DFB core when created based on the 
>associated pixel format?

Any insights into the design intentions here would be helpful and appreciated.

Thanks,
Timothy

--

Timothy Strelchun
CE Software Engineering
Digital Home Group
Intel Corporation

The views expressed above are my own and not those of Intel
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to