summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* mesa: move all vertex array functions into varray.cBrian Paul2010-05-254-273/+274
|
* mesa: added _mesa_GetVertexAttribIiv / AttribIuiv()Brian Paul2010-05-252-54/+146
| | | | Refactor the code for all the glGetVertexAttrib() functions.
* mesa: added _mesa_VertexAttribIPointer()Brian Paul2010-05-252-0/+24
|
* mesa: new GL 3.0 VertexAttrib commandsBrian Paul2010-05-251-0/+174
| | | | Still need to plug in API dispatch...
* mesa: make a bunch of shader API functions staticBrian Paul2010-05-253-377/+173
|
* mesa: display list support for uint uniformsBrian Paul2010-05-251-1/+199
| | | | Still need to plug into dispatcher...
* mesa: consolidate some glUniform codeBrian Paul2010-05-251-78/+29
|
* mesa: unsigned int uniform functions (GL3)Brian Paul2010-05-252-0/+96
|
* mesa: support for unsigned int uniformsBrian Paul2010-05-251-1/+55
|
* r300/compiler: implement SGT+SLE opcodesMarek Olšák2010-05-261-0/+20
| | | | Reported-by: Gianluca Anzolin <[email protected]>
* r300/compiler: fix dumping r5xx vertex shadersMarek Olšák2010-05-261-0/+3
|
* r300/compiler: move hardware caps to the radeon_compiler base structMarek Olšák2010-05-268-20/+23
| | | | Needed for vertex shaders too.
* r300/compiler: shorten swizzle expressionsMarek Olšák2010-05-261-44/+65
|
* rbug: add set sample mask passthrough.Dave Airlie2010-05-261-0/+12
| | | | | | This at least stops rbug segfaulting at startup. Signed-off-by: Dave Airlie <[email protected]>
* r300g: more efficient finish + fix commentsMarek Olšák2010-05-262-6/+7
|
* r300g: implement fake but compliant fencesMarek Olšák2010-05-264-35/+63
|
* r300g: add r300_init_render_functions, remove r300_render.hMarek Olšák2010-05-254-174/+84
|
* r300g: remove r300_query.hMarek Olšák2010-05-254-38/+7
|
* r300g: remove r300_flush.hMarek Olšák2010-05-254-30/+1
|
* r300g: add r300_init_blit_functions, remove r300_blit.hMarek Olšák2010-05-254-77/+28
|
* util: update comments at blitterMarek Olšák2010-05-251-1/+1
|
* util: fix indentation in blitterMarek Olšák2010-05-251-14/+14
|
* r300g,util: remove pipe_surface from the util_blitter_copy interface and ↵Marek Olšák2010-05-255-171/+151
| | | | clean up
* r300g,util: remove pipe_surface from the util_blitter_fill interface and ↵Marek Olšák2010-05-255-57/+45
| | | | clean up
* util: remove unused util_blitter_copy_surfaceMarek Olšák2010-05-251-19/+1
|
* drm_api: Remove type argument from create screen callbackJakob Bornecrantz2010-05-2512-94/+30
| | | | | With the removal of DRI1 support there where no use of this argument, some drivers didn't even properly check it.
* gallium: Remove dri1_api.h and winsys support for DRI1Jakob Bornecrantz2010-05-254-255/+7
| | | | | Since DRI1 support was dropped from st/dri it makes no sense to keep this code around.
* st/dri: Remove DRI1 supportJakob Bornecrantz2010-05-254-596/+6
| | | | | Nobody used it and the current code had been trough so many changes yet never once being tested.
* llvmpipe: Stop relying on PIPE_FLUSH_TEXTURE_CACHE/PIPE_FLUSH_RENDER_CACHE ↵José Fonseca2010-05-252-32/+11
| | | | | | | | | | magic. Flush means flush, i.e., all previous operations should be visible from other contexts. This does not imply unswizzling tiles, since unswizzling should be done on a needed basis for any context.
* gallivm: Choose an appropriate code generation optimization level.José Fonseca2010-05-251-1/+33
| | | | 'Default' unless GALLIVM_DEBUG=nopt option is set.
* sw/xlib: NULL-out pointers after freeing image dataBrian Paul2010-05-241-1/+7
| | | | | | This fixes a double-free() error when not using a shared memory XImage. The XDestroyImage() function frees the ximage->data buffer if non-NULL. If we free it ourselves, we also need to NULL-out the pointer.
* st/glx: check if deleting head of buffer listBrian Paul2010-05-241-0/+4
|
* meta: Convert Z value from normalized to object-space in meta codeBrian Paul2010-05-241-4/+19
| | | | | | | | | | | | | | Convert Z from a normalized value in the range [0, 1] to an object-space Z coordinate in [-1, +1] so that drawing at the new Z position with the default/identity ortho projection results in the original Z value. Used by the meta-Clear, Draw/CopyPixels and Bitmap functions where the Z value comes from the clear value or raster position. Fixes piglit tests fdo23670-depth_test, quad-invariance and glsl-orangebook-ch06-bump as well as oglc zbfunc.c. https://bugs.freedesktop.org/show_bug.cgi?id=23670
* mesa: Reenable check for GL_FRAMEBUFFER_INCOMPLETE_DRAW_BUFFER_EXTKristian Høgsberg2010-05-241-21/+23
| | | | | | | | The check was disabled when FEATURE_OES_framebuffer_object was enabled, since that used to mean we weren't implementing regular OpenGL semantics. Now that we can compile in support for multiple APIs, change the #ifdef to compile the check in when FEATURE_GL is enabled and enable the check for contexts that implement OpenGL at runtime.
* glsl: silence unused var warningsBrian Paul2010-05-242-0/+4
|
* llvmpipe: Also test compressed formats in lp_test_format()José Fonseca2010-05-241-0/+2
|
* llvmpipe: Fix lp_test_format on 32bit OSes.José Fonseca2010-05-241-1/+1
|
* xorg-vmwgfx: Add vmwctrl protoJakob Bornecrantz2010-04-309-0/+760
|
* mesa: Handle FEATURE_es2_glsl differences at runtime tooKristian Høgsberg2010-05-245-29/+53
| | | | | | | Now that we can support different APIs at runtime, we need to check the context for the API we're currently providing as well. https://bugs.freedesktop.org/show_bug.cgi?id=28194
* llvmpipe: Delete extraneous arugment too.José Fonseca2010-05-241-1/+1
|
* llvmpipe: Remove unused sincos_test_case struct.José Fonseca2010-05-241-6/+2
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-15 07:51:00 +0000