| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Fixes width of non-smooth (aliased) lines on nvc0.
|
|
|
|
|
|
|
|
|
| |
Fixes issues in e.g. nexuiz (desertfactory) or supertuxkart that
look like lighting bugs.
They're not visible with the software rasterizers because their
notion of linear interpolation seems to be different from that
of nv50/nvc0.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 437c748bf5072d2bded77a00c74c51cdb8b510e5.
The commit is wrong for several reasons. One of them is when we grab
a new buffer, we should update all the states it is bound in,
including all parallel contexts. I don't think this is even doable.
The correct solution would be upload data via a temporary buffer and
do resource_copy_region to the original one.
https://bugs.freedesktop.org/show_bug.cgi?id=36088
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=36086
|
|
|
|
|
|
|
| |
No idea why it's so hard to reproduce.
Broken with: c35572352e3e92683988ee8d151b47f4190d62f9
Thanks to Toni Spets for assistance.
|
| |
|
| |
|
|
|
|
| |
r300_update_hyperz_state is no longer required to be called here.
|
|
|
|
|
| |
Signed-off-by: Brian Paul <[email protected]>
Signed-off-by: Marek Olšák <[email protected]>
|
| |
|
|
|
|
| |
Signed-off-by: Brian Paul <[email protected]>
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This fixes piglit fbo/fbo-drawbuffers-blend-add.
Signed-off-by: Henri Verbeet <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
| |
Observe the actual type hierarchy and polymorphism of sampler views and
surface state.
s/texture/resource/
etc.
|
|
|
|
|
|
|
| |
This reverts commit dcdf94c87c087186f963b6e201b2989c61a76ef0.
No retrace support anymore, so human-legible representation of blend
state is much more useful than a blob.
|
|
|
|
|
|
|
|
|
| |
Because:
- bindings are not fully automatic, and they are broken most of the time
- unit tests/samples can be written in C on top of graw
- tracing/retracing is more useful at API levels with stable ABIs such as
GL, producing traces that cover more layers of the driver stack and and
can be used for regression testing
|
| |
|
| |
|
|
|
|
| |
No one uses it now, but I will need it for a lowering pass.
|
| |
|
|
|
|
| |
Signed-off-by: Alex Deucher <[email protected]>
|
|
|
|
|
| |
Improves frame rate in apps with at least one user vertex buffer and
a hw index buffer.
|
| |
|
|
|
|
| |
NOTE: This is a candidate for the stable branches.
|
|
|
|
| |
Shouldn't happen, but you never know.
|
| |
|
|
|
|
| |
We already have pb_buffer::reference::count.
|
| |
|
| |
|
| |
|
|
|
|
| |
Based on some code and ideas from Keith Whitwell.
|
| |
|
|
|
|
|
| |
Some GPUs can't do it (I think most of DX9 ones), so they should have
the option not to allow it.
|
| |
|
|
|
|
|
|
|
| |
Should fix gnome-shell's fade shader.
Unification of the shader backend which is supposed to remove the
code duplication is still WIP.
|
|
|
|
|
|
|
|
|
|
| |
Because
fetch_count = max_index - min_index + 1
overflows for min_index = 0 and max_index = 0xffffffff.
Fixes fdo 35815.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(some little changes by Marek Olšák)
Squashed commit of the following:
commit 737c0c6b7d591ac0fc969a7590e1691eeef0ce5e
Author: Luca Barbieri <[email protected]>
Date: Fri Aug 27 02:13:57 2010 +0200
draw: disable SSE and PPC paths (use LLVM instead)
These paths don't support vertex clamping, and are anyway
obsoleted by LLVM.
If you want to re-enable them, add vertex clamping and test that it
works with the ARB_color_buffer_float piglit tests.
commit fed3486a7ca0683b403913604a26ee49a3ef48c7
Author: Luca Barbieri <[email protected]>
Date: Thu Aug 26 18:27:38 2010 +0200
draw_llvm: respect vertex color clamp
commit ef0efe9f3d1d0f9b40ebab78940491d2154277a9
Author: Luca Barbieri <[email protected]>
Date: Thu Aug 26 18:26:43 2010 +0200
draw: respect vertex clamping in interpreter path
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Macro can lead to hard to debug list bugs. For instance consider
the following :
LIST_ADD(item, list->prev)
3 instruction of the macro became :
(list->prev)->next->prev = item
which is equivalent to :
list->prev = item
Thus list prev field changes and next instruction in the macro
(list->prev)->next = item
became :
item->next = item
And you endup with list corruption, other case lead to similar
list corruption. Inline function are not affected by this short
coming
Signed-off-by: Jerome Glisse <[email protected]>
|