Age | Commit message (Collapse) | Author | |
---|---|---|---|
2010-05-29 | nv50: adapt to clear interface changes | Roland Scheidegger | |
should support separate depth/stencil clears just fine. | |||
2010-05-29 | nvfx: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | svga: adapt to clear interface changes | Roland Scheidegger | |
this should support separate stencil/depth clears just fine. | |||
2010-05-29 | softpipe: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | rbug: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | trace: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | identity: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | fo: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | cell: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | st/python: adapt to clear interface changes | Roland Scheidegger | |
2010-05-29 | st/mesa: use new ability to clear only depth or stencil | Roland Scheidegger | |
2010-05-29 | util: adapt to clear interface changes | Roland Scheidegger | |
2010-05-28 | gallium: clear interface changes | Roland Scheidegger | |
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. | |||
2010-05-25 | mesa: move all vertex array functions into varray.c | Brian Paul | |
2010-05-25 | mesa: added _mesa_GetVertexAttribIiv / AttribIuiv() | Brian Paul | |
Refactor the code for all the glGetVertexAttrib() functions. | |||
2010-05-25 | mesa: added _mesa_VertexAttribIPointer() | Brian Paul | |
2010-05-25 | mesa: new GL 3.0 VertexAttrib commands | Brian Paul | |
Still need to plug in API dispatch... | |||
2010-05-25 | mesa: make a bunch of shader API functions static | Brian Paul | |
2010-05-25 | mesa: display list support for uint uniforms | Brian Paul | |
Still need to plug into dispatcher... | |||
2010-05-25 | mesa: consolidate some glUniform code | Brian Paul | |
2010-05-25 | mesa: unsigned int uniform functions (GL3) | Brian Paul | |
2010-05-25 | mesa: support for unsigned int uniforms | Brian Paul | |
2010-05-26 | r300/compiler: implement SGT+SLE opcodes | Marek Olšák | |
Reported-by: Gianluca Anzolin <gianluca@sottospazio.it> | |||
2010-05-26 | r300/compiler: fix dumping r5xx vertex shaders | Marek Olšák | |
2010-05-26 | r300/compiler: move hardware caps to the radeon_compiler base struct | Marek Olšák | |
Needed for vertex shaders too. | |||
2010-05-26 | r300/compiler: shorten swizzle expressions | Marek Olšák | |
2010-05-26 | rbug: add set sample mask passthrough. | Dave Airlie | |
This at least stops rbug segfaulting at startup. Signed-off-by: Dave Airlie <airlied@redhat.com> | |||
2010-05-26 | r300g: more efficient finish + fix comments | Marek Olšák | |
2010-05-26 | r300g: implement fake but compliant fences | Marek Olšák | |
2010-05-25 | r300g: add r300_init_render_functions, remove r300_render.h | Marek Olšák | |
2010-05-25 | r300g: remove r300_query.h | Marek Olšák | |
2010-05-25 | r300g: remove r300_flush.h | Marek Olšák | |
2010-05-25 | r300g: add r300_init_blit_functions, remove r300_blit.h | Marek Olšák | |
2010-05-25 | util: update comments at blitter | Marek Olšák | |
2010-05-25 | util: fix indentation in blitter | Marek Olšák | |
2010-05-25 | r300g,util: remove pipe_surface from the util_blitter_copy interface and ↵ | Marek Olšák | |
clean up | |||
2010-05-25 | r300g,util: remove pipe_surface from the util_blitter_fill interface and ↵ | Marek Olšák | |
clean up | |||
2010-05-25 | util: remove unused util_blitter_copy_surface | Marek Olšák | |
2010-05-25 | drm_api: Remove type argument from create screen callback | Jakob Bornecrantz | |
With the removal of DRI1 support there where no use of this argument, some drivers didn't even properly check it. | |||
2010-05-25 | gallium: Remove dri1_api.h and winsys support for DRI1 | Jakob Bornecrantz | |
Since DRI1 support was dropped from st/dri it makes no sense to keep this code around. | |||
2010-05-25 | st/dri: Remove DRI1 support | Jakob Bornecrantz | |
Nobody used it and the current code had been trough so many changes yet never once being tested. | |||
2010-05-25 | llvmpipe: Stop relying on PIPE_FLUSH_TEXTURE_CACHE/PIPE_FLUSH_RENDER_CACHE ↵ | José Fonseca | |
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. | |||
2010-05-25 | gallivm: Choose an appropriate code generation optimization level. | José Fonseca | |
'Default' unless GALLIVM_DEBUG=nopt option is set. | |||
2010-05-24 | sw/xlib: NULL-out pointers after freeing image data | Brian Paul | |
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. | |||
2010-05-24 | st/glx: check if deleting head of buffer list | Brian Paul | |
2010-05-24 | meta: Convert Z value from normalized to object-space in meta code | Brian Paul | |
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 | |||
2010-05-24 | mesa: Reenable check for GL_FRAMEBUFFER_INCOMPLETE_DRAW_BUFFER_EXT | Kristian Høgsberg | |
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. | |||
2010-05-24 | glsl: silence unused var warnings | Brian Paul | |
2010-05-24 | llvmpipe: Also test compressed formats in lp_test_format() | José Fonseca | |
2010-05-24 | llvmpipe: Fix lp_test_format on 32bit OSes. | José Fonseca | |