AFAIK buffer that is fed to SurfaceFlinger usually contains raw pixels. Here's a nice article about graphics architecture that should answer your questions. http://source.android.com/devices/graphics/architecture.html
On Thursday, 9 April 2015 21:59:52 UTC+3, Eyal Bellisha wrote: > > Hi, > I have a few questions regarding the SurfaceFlinger: > 1) I understand that the app writes to the Surface itself and then moves > the buffer to the SurfaceFlinger (let's assume I am using a Hardware Canvas > or EGL). What is inside the buffer? raw pixels? compiled openGL code? > Can the buffer hold pixels on one transaction and another type of data on > another? > 2) I read somewhere that the SurfaceFlinger writes to the > HWC/DisplayController commands using the OpenGL ES 1.0 API. Is that true? > If it is, then how are version 3.0 commands translated into version 1.0 > commands, and where? > > Thank you > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
