summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* i965simple: use u_reduced_prim() functionBrian Paul2009-06-191-16/+3
|
* draw: use u_reduced_prim() functionBrian Paul2009-06-194-28/+4
|
* softpipe: use u_reduced_prim()Brian Paul2009-06-191-15/+2
|
* gallium/util: s/boolean/unsigned/Brian Paul2009-06-191-1/+1
|
* softpipe: whitespace, reformattingBrian Paul2009-06-191-8/+5
|
* Merge branch 'ext-provoking-vertex'Brian Paul2009-06-1936-2882/+3975
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: docs/relnotes-7.6.html progs/tests/Makefile src/gallium/drivers/softpipe/sp_prim_vbuf.c src/glx/x11/indirect.c src/mesa/glapi/Makefile src/mesa/glapi/dispatch.h src/mesa/glapi/glapioffsets.h src/mesa/glapi/glapitable.h src/mesa/glapi/glapitemp.h src/mesa/glapi/glprocs.h src/mesa/main/dlist.c src/mesa/main/enums.c src/mesa/sparc/glapi_sparc.S src/mesa/x86-64/glapi_x86-64.S src/mesa/x86/glapi_x86.S
| * draw: use flatfirst variableBrian Paul2009-06-181-1/+1
| |
| * draw: remove debug codeBrian Paul2009-06-181-7/+0
| |
| * draw: fix first provoking vertex mode for quads, quad strips and polygonsBrian Paul2009-06-181-18/+55
| |
| * draw: fix first provoking vertex mode for unfilled quadsBrian Paul2009-06-181-10/+24
| |
| * mesa: fix first provoking vertex mode for unfilled tri stripsBrian Paul2009-06-181-10/+16
| |
| * draw: clean up indentationBrian Paul2009-06-181-11/+11
| |
| * st/mesa: enable EXT_provoking_vertexBrian Paul2009-06-091-0/+1
| |
| * tests: prim.c demo, modified for GL_EXT_provoking_vertexBrian Paul2009-06-092-0/+560
| |
| * tests: need tkmap.c for prim.cBrian Paul2009-06-091-0/+71
| |
| * draw: implement flatshade_first for drawing pipelineBrian Paul2009-06-092-20/+67
| |
| * softpipe: implement flatshade_first for trianglesBrian Paul2009-06-091-58/+182
| |
| * softpipe: implement flatshade_first for line setupBrian Paul2009-06-091-1/+4
| |
| * Revert "softpipe: fix flat shading provoking vertex for PIPE_PRIM_POLYGON"Brian Paul2009-06-033-6/+1
| | | | | | | | This reverts commit 5d75124db480b37977c353511b4e228905b7cc95.
| * mesa: fix parity error for tri strips with 1st provoking vertexBrian Paul2009-06-031-1/+1
| |
| * tnl: fix first provoking vertex case for unfilled trianglesBrian Paul2009-06-031-1/+1
| |
| * tnl: fix first provoking vertex bug for line loopsBrian Paul2009-06-031-1/+1
| |
| * docs: implemented GL_EXT_provoking_vertexBrian Paul2009-06-011-0/+2
| |
| * mesa: enable GL_EXT_provoking_vertex for sw driversBrian Paul2009-06-011-0/+1
| |
| * tnl: implement GL_EXT_provoking_vertexBrian Paul2009-06-011-17/+66
| |
| * st: set pipe_rasterizer_state::flatshade_first according to provoking vertex ↵Brian Paul2009-05-281-0/+3
| | | | | | | | state
| * mesa: glGet queries for GL_EXT_provoking_vertexBrian Paul2009-05-282-0/+31
| |
| * mesa: exec/dlist functions for glProvokingVertexEXT()Brian Paul2009-05-284-9/+77
| |
| * mesa: data structure updates for GL_EXT_provoking_vertexBrian Paul2009-05-283-0/+9
| |
| * mesa: regenerated enums for GL_EXT_provoking_vertexBrian Paul2009-05-281-2350/+2362
| |
| * mesa: regenerated API files for GL_EXT_provoking_vertexBrian Paul2009-05-285-102/+87
| |
| * mesa: GL API changes for GL_EXT_provoking_vertexBrian Paul2009-05-287-336/+357
| | | | | | | | This creates the new glProvokingVertexEXT() entrypoint.
* | gallium dri st: Probe the driver for supported surface formats.Thomas Hellstrom2009-06-174-63/+114
| | | | | | | | | | | | | | | | | | | | | | | | This is done when constructing the fbconfigs, and the result is saved for window system framebuffer creation. Note: For dri2 the server needs to have an identical format selection logic. Otherwise the dri state-tracker and the xorg driver (state-tracker) will disagree on which format to use for the attachments. Some more work is needed in this area. Signed-off-by: Thomas Hellstrom <[email protected]>
* | mesa driconf: Add macro to specify an option with a quoted default value.Thomas Hellstrom2009-06-171-0/+4
| | | | | | | | | | | | | | | | | | | | The default values true and false will expand to "1" and "0" when gcc -std=c99, causing bool option defaults to generate runtime failures. One solution is to specify bool option defaults quoted as "true" and "false". Add a macro to assist this. Signed-off-by: Thomas Hellstrom <[email protected]>
* | progs/rbug: Add small program to add block rulesJakob Bornecrantz2009-06-183-0/+88
| |
* | i965: Add decode for the G4X x,y offset in surface state.Eric Anholt2009-06-171-0/+2
| |
* | i965: Fix up texture layout for small things with wide pitches (tiled)Eric Anholt2009-06-171-1/+1
| | | | | | | | | | | | | | We were packing according to the pitch, while the hardware appears to base it on the base level width. With this and the previous commit, fbo-cubemap now matches untiled behavior.
* | i965: Fall back or appropriately adjust offsets of drawing to tiled regions.Eric Anholt2009-06-173-3/+54
| | | | | | | | | | | | 3D rendering to tiled textures was being done with non-tile-aligned offsets. The G4X hardware has fields to let us support it easily and correctly, while the pre-G4X hardware requires a path full of suffering, so we just fall back.
* | r300: use vbo_split_prims to split up large vertex buffers.Dave Airlie2009-06-182-2/+11
| | | | | | | | This lets ut2004 avoid hitting the elt warning.
* | i965: Fix tiling for FBO depth attachments by making DEPTH_COMPONENT Y tiled.Eric Anholt2009-06-172-4/+8
| | | | | | | | | | This may hurt if miptree relayout occurs, since we can't blit Y tiled objects. But it corrects depth tests on FBOs using textures.
* | radeon: don't re-add BOs to validate listDave Airlie2009-06-181-0/+7
| | | | | | | | | | | | if its on the list its on the list don't go readding it. multitexturing from the same texture could cause this.
* | glsl: call _mesa_postprocess_program(), disabledBrian Paul2009-06-171-0/+8
| |
* | mesa: silence warningBrian Paul2009-06-171-0/+2
| |
* | mesa: added _mesa_postprocess_program() to aid shader debuggingBrian Paul2009-06-172-0/+60
| |
* | radeon: Flush command buffer on viewport changeJerome Glisse2009-06-171-0/+1
| | | | | | | | | | | | We flush the command buffer so we don't emit mixed state (with new and previous buffer size) command buffer, this is especialy affecting zbuffer states.
* | r300: don't emit vap index offset on r5xx hw when using csJerome Glisse2009-06-171-1/+1
| | | | | | | | | | | | | | vap index offset is programmed to 0 by the kernel, it would add work to kernel checker to allow userspace programming of this so it's now disallowed with CS on KMS.
* | GLX: attempt to fix glean makeCurrent test cases.Dave Airlie2009-06-172-2/+6
| | | | | | | | | | | | | | | | | | | | | | Two parts to this: One we don't keep pointers to possibly freed memory anymore once we unbind the drawables from the context. Brian I need to figure out what the comment you made there, can we get a glean/piglit test so we can fix it properly? If the new gc is the same as the oldGC, we call the unbind even though we just bound it in that function. doh.
* | radeon: fix warnings in wrapper with libdrmDave Airlie2009-06-171-15/+15
| |
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-06-1626-105/+215
|\ \ | | | | | | | | | | | | | | | Conflicts: src/mesa/main/api_validate.c
| * | i965: fix bugs in projective texture coordinatesBrian Paul2009-06-165-20/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For the TXP instruction we check if the texcoord is really a 4-component atttibute which requires the divide by W step. This check involved the projtex_mask field. However, the projtex_mask field was being miscalculated because of some confusion between vertex program outputs and fragment program inputs. 1. Rework the size_masks calculation so we correctly set bits corresponding to fragment program input attributes. 2. Rename projtex_mask to proj_attrib_mask since we're interested in more than just texcoords (generic varying vars too). 3. Simply the indexing of the size_masks and proj_attrib_mask fields. 4. The tracker::active[] array was mis-dimensioned. Use MAX_PROGRAM_TEMPS instead of a magic number. 5. Update comments, add new assertions. With these changes the Lightsmark demo/benchmark renders correctly, until we eventually hit a GPU lockup...