an, I believe setting the surface PUSH_BUFFERS flag tells surface flinger that another component is going to provide a buffer heap and indeed use that buffer heap as the means of transferring surface data to it. At least that is how the camera service component transfers preview frames to surface flinger (assuming no overlay exists). Exactly what surface flinger does with that information is not something I have ever investigated, but it would seem reasonable that surface flinger would not need to allocate frame buffers for that type of surface.
Steve. On Dec 8, 11:18 pm, android-newbie <[email protected]> wrote: > Can someone please help me to understand this? When my > CameraSurfaceView is of type SURFACE_TYPE_PUSH_BUFFERS, does Surface > Flinger actually allocate 2 buffers for this surface? > > Thanks > an -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
