-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/27/2011 06:47 AM, Brian Paul wrote: > On Sat, Aug 27, 2011 at 1:57 AM, Ian Romanick <i...@freedesktop.org> wrote: >> From: Ian Romanick <ian.d.roman...@intel.com> >> >> The following extensions are always enabled, and drivers do not have >> to option to disable them: >> >> GL_ARB_vertex_program >> GL_EXT_gpu_program_parameters >> GL_NV_vertex_program > > It seems that the assumption here is that we'll support these > extensions in all drivers for the foreseeable future. > > I'm thinking ahead a bit to OpenGL 3.2 and core profiles. When we get > to 3.2 support, I'd like to support core profile contexts which won't > have these legacy extensions. So when someone creates a 3.2 core > profile context and accidentally does > glEnable(GL_VERTEX_PROGRAM_TWO_SIDE_ARB) we should catch that and > generate an error. > > If we're removing the internal flags and checks for these extensions, > how would we do that?
That's a good point, and I think this is similar to Chia-I's comment on patch 03/21 about OpenGL ES. What we currently have isn't very maintainable for either situation. Each driver has to maintain a different set of extensions that it exposes in different APIs / contexts. I have a couple ideas of how we could accomplish that, but I want to spend a little more time looking into each to see the possible implications. I'll spin a reduced version of this series that should be less objectionable. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk5cB/4ACgkQX1gOwKyEAw+pNACfZOxS/MI8j808BfwZy6f3qQgv j5oAn3e/+ggOhnk+i/F27r5OI99seaNJ =DdrG -----END PGP SIGNATURE----- _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev