On Tue, Mar 31, 2009 at 04:03:31AM -0700, pixelflinger wrote: > This is an "extension" we're using to avoid making a copy of the > texture data, it is only used by SurfaceFlinger; the texture data > needs to be allocated in a special way for this to work. Originally, > SurfaceFlinger was going to use OpenGL ES for the composition on the > G1, but we found out that it was a lot faster and a lot more power- > efficient to use the 2D blitter (copybit). In the end, this > "extension" is now only used by the software renderer on h/w that > doesn't have GL or copybit capabilities. > You can think of it as "old cruft" that never was cleaned up; since, > in practice this extension isn't used in any shipping device... and > never will, because... > ... it is going away post-cupcake and is replaced by the (well > documented and official) EGL_image_base (and family) extensions. I am interested in the status of the switch. Is there anything that can be shared?
I am also planning to hack on SurfaceFlinger to add compiz-like[1] visual effects. My platform is x86, but I think there should be no significant differences in this regard. For my purpose, I have been porting intel OpenGL driver to android and adding support for OpenGL ES, OES_draw_texture, and OES_EGL_image[2]. So far, I am able to fully accelerate surfaceflinger, and it seems to work fine. [1] http://www.compiz-fusion.org/ [2] http://www.gitorious.org/android-eeepc/mesa/commits/mesa-es -- Regards, olv --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
