[Mesa-dev] [RFC] [PATCH 1/2] mesa: let GL3 buf obj queries not depend on opengl major version
brianp at vmware.com
Mon Sep 19 10:15:01 PDT 2011
On 09/19/2011 10:17 AM, Ian Romanick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 09/19/2011 07:20 AM, Brian Paul wrote:
>> On 09/19/2011 04:25 AM, Yuanhan Liu wrote:
>>> If I understand correctly, the new GL3 buffer object queries
>>> parameters, like BUFFER_MAP_ACCESS_FLAGS, depends on
>>> ARB_map_buffer_range extension.
>> That would make sense, but in fact the extension spec
>> says nothing about these queries. They were added in GL 3.0.
> It seems like this could be an error in the extension spec. This is
> one of the extensions, like ARB_framebuffer_object, that "back ports"
> OpenGL 3.0 functionality to previous versions. These extensions are
> supposed to provide *identical* functionality to OpenGL 3.0. The
> other cases of mismatches have been determined to be bugs in the
> extension specs.
> The question is, what do other implementations do? The other other
> question is, are there any implementations that support
> ARB_map_buffer_range but not OpenGL 3.0?
I'm sure the ARB would agree that omitting the queries was an
oversight and that they should be there.
I'd be OK with just adding them but if we want to be consistent with
other implementations and omit them, I could live with that. Nobody's
seemed to complain/notice so far.
More information about the mesa-dev