summaryrefslogtreecommitdiffstats
path: root/src/gallium/auxiliary/util/u_cache.c
diff options
context:
space:
mode:
authorIan Romanick <[email protected]>2012-12-01 10:50:57 -0800
committerIan Romanick <[email protected]>2012-12-03 21:24:54 -0800
commita13f9dfbb88720c9ccca443e834106a80e69fedb (patch)
tree5c4973c96fb2dea6ac58d822dfe49966edd4c601 /src/gallium/auxiliary/util/u_cache.c
parent4d2f04cd6cb2fbaee54ab6e0f84cdb576ceeadcd (diff)
mesa: Only require Gen'ed name for glBind{Framebuffer,Renderbuffer} on desktop
Desktop OpenGL implementations that support either GL_ARB_framebuffer_object or OpenGL 3.0 must require names from glGenFramebuffers for glBindFramebuffer. We have enforced this rule for quite some time. However, OpenGL ES 1.0, 2.0, and 3.0 implementations are required to allow user-defined names (e.g., not from glGenFramebuffers{OES,}). The Intel drivers have hacked around this by not enabling GL_ARB_framebuffer_object in an ES context. Instead, just pick the correct behavior in _mesa_BindFramebuffer based on the context API. Chad pointed out in a review e-mail: "I'd like to point out, though, that glBindFramebufferEXT and glBindRenderbufferEXT are still broken on desktop GL because they don't accept user-genned names. But that fix belongs to a different series." Currently glBindFramebufferEXT is an alias for glBindFramebuffer. Unalising two functions presents some difficulty, so we'll have to revisit this eventually. v2: Perform same check in _mesa_BindRenderbuffer too. Signed-off-by: Ian Romanick <[email protected]> Reviewed-by: Chad Versace <[email protected]> Reviewed-by: Matt Turner <[email protected]> Reviewed-by: Kenneth Graunke <[email protected]> [v1]
Diffstat (limited to 'src/gallium/auxiliary/util/u_cache.c')
0 files changed, 0 insertions, 0 deletions