Mathias,
This is what I needed to know. Thanks for the info.
On Mar 31, 6:03 am, pixelflinger <pixelflin...@google.com> wrote:
> Hi Jeff,
>
> 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.
>
> mathias
>
> On Mar 31, 3:36 am, "Jeff V." <jdv1...@gmail.com> wrote:
>
>
>
> > In frameworks/base/opengl/libagl/texture.cpp & frameworks/base/libs/
> > surfaceflinger/LayerBase.cpp you will see the gl extension
> > GL_DIRECT_TEXTURE_2D_QUALCOMM is being used. What exactly is this
> > extension being used for instead of just GL_TEXTURE_2D? Is there some
> > sort of optimization performed while using this extension?
>
> > Thanks.- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
