Dianne, Mathias: Thanks for your explain and reply. Now I understand the purpose of using two buffers in: "Surface".(it always has a "good" bitmap for a surface that it can composit without waiting for the applicationt) and "EGLDisplaySurface".(don't see any flicker while it is compositing)
Here I suppose: a) is "Surface"'s unprepared buffer. b) is "Surface"'s "good" buffer c) is "EGLDisplaySurface"'s buffer waiting for composit d) is "EGLDisplaySurface"'s "/dev/fdX" or "/dev/graphics/fdX" I think: all "window"'s b) would be composed to c) at some API Thanks for correct me if something is wrong here. If it is right, is it at API: SurfaceComposerClient::unlockSurface? If it is wrong, how b) composed c) BstRgds gan On Feb 1, 7:03 am, Mathias Agopian <[email protected]> wrote: > On Sat, Jan 31, 2009 at 4:54 AM, gan <[email protected]> wrote: > > > Hi: > > > I add some log in SurfaceFlinger and according to it I think(Thanks > > for correct me if something is wrong): > > a)Java "SurfaceSession" would create(native side) a > > "mSharedHeapAllocator" for each Surface client, > > This is done at native Client::Client in the process "system_server" > > b)Java "Surface" would access(native side) "mSharedHeapAllocator" to > > allocate 2 buffer > > for each Normal Surface(not Buffer,Dim or Blur) client. > > This is done at native Client::createAllocator in the process > > "system_server"'s another threads. > > > My question is: > > 1) what is the relationship of these buffers created in b) with the > > buffers swapped by EGLDisplaySurface::swapBuffers, > > These are unrelated. > > > 2) what is the relationship of these buffers with "/dev/graphics/fbX" > > or "/dev/fbX", > > These are the ones used by EGLDisplaySurface > > mathias > > > > > Thanks&BstRgds > > gan --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
