summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* r600g: adapt to interface changesRoland Scheidegger2010-06-033-22/+45
| | | | | r600g should be able to handle separate depth stencil clears as well. Also adapt surface_fill/copy stubs to new interface (not that it matters).
* Merge branch 'gallium-newclear'Roland Scheidegger2010-06-0347-336/+763
|\ | | | | | | | | Conflicts: src/gallium/state_trackers/python/p_context.i
| * gallium: rename clearRT / clearDS to clear_render_target / clear_depth_stencilRoland Scheidegger2010-06-0317-217/+217
| | | | | | | | | | more consistent with rest of gallium naming conventions. Also rename driver-internal names for these the same.
| * llvmpipe: adapt to clear interface changesRoland Scheidegger2010-05-298-28/+113
| | | | | | | | | | with some newfangled code, should support separate depth/stencil clears. Needs some testing.
| * i965g: adapt to clear interface changesRoland Scheidegger2010-05-293-12/+66
| | | | | | | | | | just like i915g, should in theory support separate depth/stencil clears (untested), with the same 2d blitter hacks.
| * i915g: adapt to clear interface changesRoland Scheidegger2010-05-297-29/+72
| | | | | | | | | | should in theory support separate depth/stencil clears (untested). Also fix some format omissions?
| * r300g: adapt to clear interface changesRoland Scheidegger2010-05-292-10/+31
| | | | | | | | should support separate depth/stencil clears just fine with changed u_blitter.
| * nv50: adapt to clear interface changesRoland Scheidegger2010-05-293-18/+22
| | | | | | | | should support separate depth/stencil clears just fine.
| * nvfx: adapt to clear interface changesRoland Scheidegger2010-05-292-11/+29
| |
| * svga: adapt to clear interface changesRoland Scheidegger2010-05-293-4/+8
| | | | | | | | this should support separate stencil/depth clears just fine.
| * softpipe: adapt to clear interface changesRoland Scheidegger2010-05-292-1/+2
| |
| * rbug: adapt to clear interface changesRoland Scheidegger2010-05-291-28/+48
| |
| * trace: adapt to clear interface changesRoland Scheidegger2010-05-291-25/+53
| |
| * identity: adapt to clear interface changesRoland Scheidegger2010-05-291-28/+48
| |
| * fo: adapt to clear interface changesRoland Scheidegger2010-05-291-1/+2
| |
| * cell: adapt to clear interface changesRoland Scheidegger2010-05-291-1/+0
| |
| * st/python: adapt to clear interface changesRoland Scheidegger2010-05-291-13/+26
| |
| * st/mesa: use new ability to clear only depth or stencilRoland Scheidegger2010-05-292-14/+32
| |
| * util: adapt to clear interface changesRoland Scheidegger2010-05-295-95/+151
| |
| * gallium: clear interface changesRoland Scheidegger2010-05-284-23/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | clears were a bit limited in gallium: - no scissoring (OGL only) nor explicit rectangle list (d3d9) - no color/stencil masks (OGL only) - no separate depth/stencil clears (d3d9/d3d10/OGL) - cannot really clear single color buffer (only with resource_fill_region) Additionally, d3d can clear surfaces not currently bound to the framebuffer. It is, however, not easy to find some common ground what a clear should be able to do, due to both API requirements and also hw differences (a case which might be able to use a special clear path on one hw might need a "normal" quad render on another). Hence several clear methods are provided, and a driver should implement all of them. - clear: slightly modified to also be able to clear only depth or stencil in a combined depth/stencil surface. This is however optional based on driver capability though ideally it wouldn't be optional. AFAIK this is in fact something used by applications quite a bit. Otherwise, for now still doesn't allow clearing with scissors/mask (or single color buffers) - clearRT: clears a single (potentially unbound) color surface. This was formerly roughly known as resource_fill_region. mesa st will not currently use this, though potentially would be useful for GL ClearBuffer. - clearDS: similar to above except for depth stencil surfaces. Note that clearDS/clearRT currently handle can handle partial clear. This might change however.
* | gallium: Don't depend directly on staging dir in Xorg template makefileJakob Bornecrantz2010-06-011-2/+2
| |
* | tgsi: we don't support indirect input/output registers in SSE codegen yetBrian Paul2010-06-031-6/+10
| | | | | | | | | | | | | | | | Extend the check for indirect addressing of temp regs to include input/output regs. Fixes failure with piglit glsl-texcoord-array.shader_test test when using SSE codegen.
* | tgsi: whitespace cleanupBrian Paul2010-06-031-14/+2
| |
* | gallium: add interpolation parameter to simple shader functionsBrian Paul2010-06-036-48/+58
| | | | | | | | | | This lets us specify linear interpolation instead of perspective interpolation for blit operations. Might be a bit faster.
* | gallium: Don't always copy the dri driver to the staging dirJakob Bornecrantz2010-06-011-2/+4
| | | | | | | | | | So something in the build keept updating the timestamp on the staging directory causing us to always copy the library to it.
* | gallium: Create a Xorg driver template MakefileJakob Bornecrantz2010-06-012-52/+82
| |
* | util/u_debug: use MAX2 macroBrian Paul2010-06-031-7/+1
| |
* | llvmpipe: Number shaders/variants for more reproducible function names in ↵José Fonseca2010-06-032-7/+28
| | | | | | | | the IR.
* | gallivm: Register the JIT engine with oprofile on debug/profile builds.José Fonseca2010-06-032-1/+30
| |
* | gallivm: Factor out the quad derivative code into a single place. Fix ddy.José Fonseca2010-06-035-52/+204
| | | | | | | | For ddy it should be (bottom - top).
* | r300g: use util/u_debugJoakim Sindholt2010-06-031-54/+5
| |
* | gallium: silence all debug_named_value related warningsJoakim Sindholt2010-06-037-80/+80
| |
* | util/u_debug: add description field to debug_named_valueJoakim Sindholt2010-06-032-6/+20
| |
* | scons: Handle Python OSError exception when missing libdrm_radeon.Vinson Lee2010-06-031-1/+5
| | | | | | | | | | Instead of crashing when libdrm_radeon is unavailable, the SCons build just does not build r600g.
* | r300/compiler: print opcode names instead of numbersMarek Olšák2010-06-033-8/+8
| |
* | r300g: set the minimum texture stride to 64 bytes on RS600, RS690, and RS740Marek Olšák2010-06-031-2/+14
| | | | | | | | I hope I've done it right. No way to test it here...
* | dri/swrast: Remove unnecessary header.Vinson Lee2010-06-021-1/+0
| |
* | st/mesa: fix indirect addressing of input/output regsBrian Paul2010-06-021-4/+9
| | | | | | | | | | | | This fixes an issue that was missed with commit 9f544394c1d059ce09c8bb2b5e11f5e871c7915f. Fixes piglit glsl-texcoord-array.shader_test
* | gallivm: bump up LP_BUILD_FLOW_MAX_VARIABLESBrian Paul2010-06-021-1/+1
| | | | | | | | | | | | | | Fixes failed assertion with piglit fbo-drawbuffers-fragcolor.c See fd.o bug 28358. With 8 color buffers + Z we need to declare 33 vars, at least.
* | intel: Remove a leftover DRI1/DRI2 conditionalKristian Høgsberg2010-06-021-7/+2
| |
* | glx: fix indentation and remove extraneous breakBrian Paul2010-06-021-2/+1
| |
* | glx: reformat and silence unused expression warningBrian Paul2010-06-021-1/+2
| |
* | glsl: handle indirectly indexed input registers in linkerBrian Paul2010-06-021-29/+108
| | | | | | | | | | | | | | | | | | | | For example, if the fragment shader reads gl_TexCoord[i] with a dynamic index we need to set all the InputsRead bits for all texcoords. We were already doing this for shader outputs. Refactored the later code so inputs and outputs are handled with similar code. Fixes a swrast failure with piglit's glsl-texcoord-array.shader_test
* | mesa: use BITFIELD64_BIT() macroBrian Paul2010-06-021-1/+1
| |
* | glsl: fix bad sanity-check assertionBrian Paul2010-06-021-1/+1
| |
* | mesa: whitespace and 80 column wrappingBrian Paul2010-06-021-3/+12
| |
* | shaders: Don't lose the param binding swizzle for single params.Eric Anholt2010-06-022-2/+2
| | | | | | | | | | | | | | | | | | Multiple item params are OK because we don't allow swizzles for them (in case you do array access to hit their elements, for example). For singles, though, using the swizzle can cut down on storage, we do want to allow a swizzled use of another param. Fixes OGLC texRect.c.
* | llvmpipe: Fix bad logic.José Fonseca2010-06-021-1/+1
| | | | | | | | Courtesy of Vinson and coverity.
* | llvmpipe: Remove unnecessary header.Vinson Lee2010-06-021-1/+0
| |
* | llvmpipe: Fix typo in assert.José Fonseca2010-06-021-1/+1
| |
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-22 12:03:40 +0000