summaryrefslogtreecommitdiff
path: root/src/mesa/main
AgeCommit message (Collapse)Author
2009-05-22mesa: add missing update_min() call in update_arrays()Brian Paul
2009-05-22mesa: reduce gl_array_object::VertexAttrib[] array from 32 to 16 elementsBrian Paul
This array was mistakenly dimensioned with VERT_ATTRIB_MAX (32) but it should really be MAX_VERTEX_GENERIC_ATTRIBS (16). The generic vertex attributes are in addition to the conventional arrays (except in NV vertex program mode- they alias/overlay in that case) so the total of all conventional attributes plus generic attributes should total 32 (not 48).
2009-05-22mesa: use Elements() for loop limitBrian Paul
2009-05-22mesa: use Elements() for loop limitBrian Paul
2009-05-22mesa: use Elements() for loop limitBrian Paul
2009-05-22mesa: simplify adjust_buffer_object_ref_counts()Brian Paul
2009-05-22mesa: minor code clean-upBrian Paul
2009-05-22mesa: use Elements() for loop limitBrian Paul
2009-05-22mesa: use Elements() for loop boundBrian Paul
2009-05-22mesa: minor code simplificationBrian Paul
2009-05-22Merge branch 'mesa_7_5_branch'Brian Paul
2009-05-22mesa: fix loop over generic attribs in update_arrays()Brian Paul
2009-05-22Merge branch 'mesa_7_5_branch'Brian Paul
2009-05-22mesa: allow GL_BITMAP type in _mesa_image_image_stride()Brian Paul
It's possible to hand a GL_COLOR_INDEX/GL_BITMAP image to glTexImage3D() which gets converted to RGBA via the glPixelMap tables. This fixes a failure with piglit/fdo10370 with Gallium.
2009-05-22mesa: added some assertionsBrian Paul
2009-05-22mesa: use Elements() macro to limit loops instead of constantsBrian Paul
2009-05-22mesa: remove MAX_VERTEX_PROGRAM_ATTRIBSBrian Paul
Use MAX_VERTEX_GENERIC_ATTRIBS instead. No need for two #defines for the same quantity.
2009-05-22mesa: rename MAX_VERTEX_ATTRIBS to MAX_VERTEX_GENERIC_ATTRIBSBrian Paul
Be clearer that this is the number of generic vertex program/shader attributes, not counting the legacy attributes (pos, normal, color, etc).
2009-05-22mesa: s/MAX_VERTEX_PROGRAM_ATTRIBS/MAX_NV_VERTEX_PROGRAM_INPUTS/ in NV funcsBrian Paul
2009-05-22mesa: added commentBrian Paul
2009-05-21mesa: add missing glGet*() case for GL_VERTEX_ARRAY_BINDING_APPLEBrian Paul
2009-05-21mesa: s/MAX_VERTEX_PROGRAM_ATTRIBS/MAX_NV_VERTEX_PROGRAM_INPUTSBrian Paul
2009-05-21mesa: freshen comments for update_array()Brian Paul
2009-05-21mesa: remove const qualifierBrian Paul
2009-05-21mesa: VertexAttribPointer commentsBrian Paul
2009-05-21mesa: call _mesa_update_array_object_max_element() before printing array infoBrian Paul
2009-05-21mesa: added gl_array_object::Weight array fieldBrian Paul
We don't really implement vertex weights but in the VBO code this fixes and odd case for the legacy_array[] setup. Before, the vbo->draw_prims() call was always indicating that the vertex weight array was present/enabled when it really wasn't.
2009-05-21mesa: check FEATURE_point_size_array for PointSize arrayBrian Paul
2009-05-21mesa: fix some potential state-restore issues in pop_texture_group()Brian Paul
Call the _mesa_set_enable() functions instead of driver functions, etc. Also, add missing code for 1D/2D texture arrays.
2009-05-21mesa: new _mesa_update_array_object_max_element() functionBrian Paul
This will replace the code in state.c
2009-05-21mesa: added debug functions for dumping color/depth/stencil buffersBrian Paul
2009-05-21mesa: remove pointless null ptr check, improved some error messagesBrian Paul
2009-05-21mesa: added _mesa_print_arrays() for debuggingBrian Paul
2009-05-21mesa: updated comment for _MaxElement fieldBrian Paul
It's the largest array index, plus one.
2009-05-21mesa: move gl_array_attrib::_MaxElement to gl_array_object::_MaxElementBrian Paul
This value is per array object.
2009-05-19Merge branch 'mesa_7_5_branch'Brian Paul
2009-05-19mesa: allow depth/stencil textures to be attached to GL_STENCIL_ATTACHMENTMathias Fröhlich
See sourceforge bug #2793846.
2009-05-19mesa: assign trb->Base.StencilBits in update_wrapper().Brian Paul
When we render to a depth/stencil texture there are stencil bits.
2009-05-19mesa: print more info when valid_texture_object() failsBrian Paul
2009-05-18Merge branch 'mesa_7_5_branch'Brian Paul
Conflicts: Makefile src/mesa/main/version.h
2009-05-18mesa: comments for _mesa_generate_mipmap_level()Brian Paul
2009-05-15mesa: Mark FBOs with compressed color attachments as FBO-incomplete.Eric Anholt
Both EXT_fbo and ARB_fbo agree on this. Fixes a segfault in the metaops mipmap generation in Intel for SGIS_generate_mipmap of S3TC textures in Regnum Online. Bug #21654.
2009-05-15mesa: bump version to 7.5-rc2Brian Paul
2009-05-13Merge branch 'mesa_7_5_branch'Brian Paul
Conflicts: src/mesa/main/arrayobj.c src/mesa/main/arrayobj.h src/mesa/main/context.c
2009-05-13mesa: delete array objects before buffer objects during context tear-downBrian Paul
The former may point to the later.
2009-05-13mesa: clean-up vertex array object VBO unbinding and delete/refcountingBrian Paul
Don't really delete vertex array objects until the refcount hits zero. At that time, unbind any pointers to VBOs. (cherry picked from commit 32b851c80792623195069d7a41a5808cff3b2f6f)
2009-05-13mesa: reference counting for gl_array_objectBrian Paul
Every kind of object that can be shared by multiple contexts should be refcounted. (cherry picked from commit 1030bf0ded2a88a5e27f7a4d393c11cfde3d3c5a)
2009-05-11mesa: updated comments for _mesa_generate_mipmap()Brian Paul
2009-05-11mesa: Fixed a texture memory leakBrian Paul
The current texture for any particular texture unit is given an additional reference in update_texture_state(); but if the context is closed before that texture can be released (which is quite frequent in normal use, unless a program unbinds and deletes the texture and renders without it to force a call to update_texture_state(), the memory is lost. This affects general Mesa; but the i965 is particularly affected because it allocates a considerable amount of additional memory for each allocated texture. (cherry picked from master, commit c230767d6956b63a2b101acb48f98823bb5dd31a)
2009-05-08mesa: Fixed a texture memory leakRobert Ellison
The current texture for any particular texture unit is given an additional reference in update_texture_state(); but if the context is closed before that texture can be released (which is quite frequent in normal use, unless a program unbinds and deletes the texture and renders without it to force a call to update_texture_state(), the memory is lost. This affects general Mesa; but the i965 is particularly affected because it allocates a considerable amount of additional memory for each allocated texture.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-05 11:50:24 +0000