[Mesa-dev] Conflicts between OES/EXT/ARB_framebuffer_object and GL3.0/GLES2

Marek Olšák maraeo at gmail.com
Thu May 3 03:36:17 PDT 2012


On Thu, May 3, 2012 at 3:32 AM, Chad Versace
<chad.versace at linux.intel.com> wrote:
>   (FYI, if I understand the gallium code, the only drivers that currently
>   enable both are Intel, swrast, and OSMesa).

Gallium also enables both if packed depth-stencil textures are
supported (which is the case with most, if not all, drivers).
Otherwise, it only enables the EXT variant.

>
> 2. Create separate entry points:
>      - _mesa_BindFramebufferEXT, which implements
>          - glBindFramebufferEXT
>          - glBindFramebufferOES
>          - glBindFramebuffer in GLES2
>      - _mesa_BindFramebufferARB, which implements
>          - glBindFramebufferARB
>          - glBindFramebuffer in GL 3.x
>
> Any opinions? (I slightly prefer 2).

FWIW, 2 seems to be a good plan to me too.

Marek


More information about the mesa-dev mailing list