URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=47b3a0d23504de43ce2dc028e84037f7cd89bd89
Author: Ian Romanick <[email protected]>
Date: Mon Nov 9 11:15:04 2015 -0800
meta: Don't save or restore the active client texture
This setting is only used by glTexCoordPointer and related glEnable
calls. Since the preceeding commits removed all of those, it is not
necessary to save, reset to default, or restore this state.
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=c63f9c735dfbd572b671f739ba5df0c2ad9a388a
Author: Ian Romanick <[email protected]>
Date: Thu Nov 5 14:48:58 2015 -0800
meta: Don't save or restore the VBO binding
Nothing left in meta does anything with the VBO binding, so we don't
need to save or restore it. The VAO binding is still modified.
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=58aa56d40bfc6ba54ad9172bf219d18eeb615a80
Author: Ian Romanick <[email protected]>
Date: Mon Nov 9 13:11:02 2015 -0800
meta/TexSubImage: Don't pollute the buffer object namespace
tl;dr: For many types of GL object, we can *NEVER* use the Gen function.
In OpenGL ES (all versions!) and OpenGL compatibility profile,
applications don't have to call Gen functions. The GL spec is very
clear about how you can mix-and-match generated names and non-generated
names: you can use any name you want for a particular object type until
you call the Gen function for that object type.
Here's the problem scenario:
- Application calls a meta function that generates a name. The first
Gen will probably return 1.
- Application decides to use the same name for an object of the same
type without calling Gen. Many demo programs use names 1, 2, 3,
etc. without calling Gen.
- Application calls the meta function again, and the meta function
replaces the data. The application's data is lost, and the app
fails. Have fun debugging that.
Signed-off-by: Ian Romanick <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92363
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=76cfe2bc4436186fd585be96c4f402c1b1c79bdf
Author: Ian Romanick <[email protected]>
Date: Thu Nov 5 14:44:26 2015 -0800
meta: Don't pollute the buffer object namespace in _mesa_meta_DrawTex
tl;dr: For many types of GL object, we can *NEVER* use the Gen function.
In OpenGL ES (all versions!) and OpenGL compatibility profile,
applications don't have to call Gen functions. The GL spec is very
clear about how you can mix-and-match generated names and non-generated
names: you can use any name you want for a particular object type until
you call the Gen function for that object type.
Here's the problem scenario:
- Application calls a meta function that generates a name. The first
Gen will probably return 1.
- Application decides to use the same name for an object of the same
type without calling Gen. Many demo programs use names 1, 2, 3,
etc. without calling Gen.
- Application calls the meta function again, and the meta function
replaces the data. The application's data is lost, and the app
fails. Have fun debugging that.
Signed-off-by: Ian Romanick <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92363
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=a222d4cbc3de49857aebbdf727e53c273abcc6c1
Author: Ian Romanick <[email protected]>
Date: Thu Nov 5 14:42:07 2015 -0800
meta: Use internal functions for buffer object and VAO access in
_mesa_meta_DrawTex
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=b8a7369fb7e5773892d01fcb1140fe6569ee27eb
Author: Ian Romanick <[email protected]>
Date: Thu Nov 5 14:31:23 2015 -0800
meta: Track VBO using gl_buffer_object instead of GL API object handle in
_mesa_meta_DrawTex
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=d5225ee5d92f00958c54b425fe829c811149e889
Author: Ian Romanick <[email protected]>
Date: Thu Nov 5 14:16:31 2015 -0800
meta: Partially convert _mesa_meta_DrawTex to DSA
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=37d11b13ce1db2ad867ff5433cb31bcd1d93c7bf
Author: Ian Romanick <[email protected]>
Date: Tue Nov 3 17:41:16 2015 -0800
meta: Don't pollute the buffer object namespace in
_mesa_meta_setup_vertex_objects
tl;dr: For many types of GL object, we can *NEVER* use the Gen function.
In OpenGL ES (all versions!) and OpenGL compatibility profile,
applications don't have to call Gen functions. The GL spec is very
clear about how you can mix-and-match generated names and non-generated
names: you can use any name you want for a particular object type until
you call the Gen function for that object type.
Here's the problem scenario:
- Application calls a meta function that generates a name. The first
Gen will probably return 1.
- Application decides to use the same name for an object of the same
type without calling Gen. Many demo programs use names 1, 2, 3,
etc. without calling Gen.
- Application calls the meta function again, and the meta function
replaces the data. The application's data is lost, and the app
fails. Have fun debugging that.
Signed-off-by: Ian Romanick <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92363
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=b1b73a42c8f245d5bf6bbed04071b2c6519b2fb4
Author: Ian Romanick <[email protected]>
Date: Tue Nov 3 16:47:22 2015 -0800
meta: Use internal functions for buffer object and VAO access
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=52921f8e089abbc6871060fc50f90b62aaf1e11b
Author: Ian Romanick <[email protected]>
Date: Tue Nov 3 15:55:14 2015 -0800
meta: Use DSA functions for VBOs in _mesa_meta_setup_vertex_objects
The fixed-function attribute paths don't get the DSA treatment because
there are no DSA entry-points for fixed-function attributes. These
could have been added, but this is a temporary patch intended to make
later patches easier to review.
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=1035e00a815f0babddac0c6c43d01fd34f7e8a94
Author: Ian Romanick <[email protected]>
Date: Tue Nov 3 15:37:40 2015 -0800
meta: Track VBO using gl_buffer_object instead of GL API object handle
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=3b5a7d450dea9bfadf1d72338f4418c87340805b
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 20:11:02 2015 -0800
meta: Don't leave the VBO bound after _mesa_meta_setup_vertex_objects
Meta currently does this, but future changes will make this impossible.
Explicitly do it as a step in the patch series now to catch any possible
kinks.
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=ed0bd6573b6ce83471e73d009dbab5220f9e80c0
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 19:10:08 2015 -0800
i965: Use _mesa_NamedBufferSubData for users of
_mesa_meta_setup_vertex_objects
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=7f2f3000716d994d94c53f4a0c8a211fb00a46a4
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 18:36:34 2015 -0800
meta: Use _mesa_NamedBufferData and _mesa_NamedBufferSubData for users of
_mesa_meta_setup_vertex_objects
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=89a61afdd7346d6e36caccc4d6f2a2607dc4a1f6
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 18:33:54 2015 -0800
meta: Use DSA functions for PBO in create_texture_for_pbo
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=4e6b9c11fc545cc570ea0042af93e61bfb525d34
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 17:04:41 2015 -0800
i965: Don't pollute the buffer object namespace in brw_meta_fast_clear
tl;dr: For many types of GL object, we can *NEVER* use the Gen function.
In OpenGL ES (all versions!) and OpenGL compatibility profile,
applications don't have to call Gen functions. The GL spec is very
clear about how you can mix-and-match generated names and non-generated
names: you can use any name you want for a particular object type until
you call the Gen function for that object type.
Here's the problem scenario:
- Application calls a meta function that generates a name. The first
Gen will probably return 1.
- Application decides to use the same name for an object of the same
type without calling Gen. Many demo programs use names 1, 2, 3,
etc. without calling Gen.
- Application calls the meta function again, and the meta function
replaces the data. The application's data is lost, and the app
fails. Have fun debugging that.
Signed-off-by: Ian Romanick <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92363
Reviewed-by: Abdiel Janulgue <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=e62799bd4e7b7525995e465a4bdcf6df0b0a69a0
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 14:49:03 2015 -0800
i965: Use internal functions for buffer object access
Instead of going through the GL API implementation functions, use the
lower-level functions. This means that we have to keep track of a
pointer to the gl_buffer_object and the gl_vertex_array_object.
This has two advantages. First, it avoids a bunch of CPU overhead in
looking up objects and validing API parameters. Second, and much more
importantly, it will allow us to stop calling _mesa_GenBuffers /
_mesa_CreateBuffers and pollute the buffer namespace (next patch).
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Abdiel Janulgue <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=1c5423d3a074d50138e5ad7945024f9cf4d063ec
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 14:31:56 2015 -0800
i965: Use DSA functions for VBOs in brw_meta_fast_clear
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Abdiel Janulgue <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=dcadd855f14b0d3dcce04a16afdfed2d7159d4a8
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 12:41:28 2015 -0800
i965: Pass brw_context instead of gl_context to brw_draw_rectlist
Future patches will use the brw_context instead. Keeping this
non-functional change separate should make the function changes easier
to review.
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Abdiel Janulgue <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=4a644f1caadc6b3e26b5f0ac60ac855152e38e59
Author: Ian Romanick <[email protected]>
Date: Tue Nov 3 16:16:00 2015 -0800
mesa: Refactor enable_vertex_array_attrib to make
_mesa_enable_vertex_array_attrib
Pulls the parts of enable_vertex_array_attrib that aren't just parameter
validation out into a function that can be called from other parts of
Mesa (e.g., meta).
_mesa_enable_vertex_array_attrib can also be used to enable
fixed-function arrays.
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=a336fcd36a4743c1ea6f8549cb31b48277359717
Author: Ian Romanick <[email protected]>
Date: Tue Nov 3 16:09:22 2015 -0800
mesa: Refactor update_array_format to make _mesa_update_array_format_public
Pulls the parts of update_array_format that aren't just parameter
validation out into a function that can be called from other parts of
Mesa (e.g., meta).
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=8fae494df2813bfa38f1aabd6c9b3c1ba3a5e4ef
Author: Ian Romanick <[email protected]>
Date: Mon Nov 2 12:40:32 2015 -0800
mesa: Make bind_vertex_buffer avilable outside varray.c
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Abdiel Janulgue <[email protected]>
Reviewed-by: Anuj Phogat <[email protected]>
_______________________________________________
mesa-commit mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-commit
