Lines Matching full:gles
7 Hardware GLES emulation in the Android platform is implemented with a mix
10 - Several host "translator" libraries. They implement the EGL, GLES 1.1 and
11 GLES 2.0 ABIs defined by Khronos, and translate the corresponding function
15 - desktop GL 2.0 for GLES 1.1 and GLES 2.0
20 | EGL | | GLES 1.1 | | GLES 2.0 | TRANSLATOR
33 the same EGL / GLES 1.1 and GLES 2.0 ABIs.
35 They collect the sequence of EGL/GLES function calls and translate then
48 | EGL | | GLES 1.1 | | GLES 2.0 | SYSTEM
81 - The renderer decodes the EGL/GLES commands from the wire
97 | EGL | | GLES 1.1 | | GLES 2.0 | TRANSLATOR
113 | EGL | | GLES 1.1 | | GLES 2.0 | SYSTEM
145 | EGL | | GLES 1.1 | | GLES 2.0 | TRANSLATOR
184 system and the renderer. This also avoids adding lots of GLES-specific
187 2 - The ability to use vendor-specific desktop EGL/GLES libraries is
191 EGL/GLES libraries that emulate their respectivie embedded graphics
228 $QEMU/hw/opengles.c -> implement GLES initialization
254 libGLES_CM_translator -> GLES 1.1 translation
255 libGLES_V2_translator -> GLES 2.0 translation
282 - EGL/GLES function calls are described through several "specification"
291 files. They contain code that can serialize EGL/GLES calls into simple
378 For GLES 1.1:
383 For GLES 2.0:
423 Meta EGL/GLES system libraries, and egl.cfg:
426 It is important to understand that the emulation-specific EGL/GLES libraries
428 provides a set of "meta" EGL/GLES libraries that will load the appropriate
434 - hardware-specific EGL/GLES libraries
451 system's EGL/GLES libraries don't support anything else.
505 In addition to EGL/GLES libraries, the Android system requires a
518 GLES emulation project. It's not very long, but there are a few things to
567 - Provide a way to listen to incoming EGL/GLES commands from the guest.
603 There is also some support code for the display of the GLES framebuffer
