| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Include p_screen.h for complete type to pipe_screen.
|
|
|
|
|
|
| |
Update all drivers to use draw_set_index_buffer,
draw_set_mapped_index_buffer, and draw_vbo. Remove
draw_set_mapped_element_buffer and draw_set_mapped_element_buffer_range.
|
|
|
|
|
|
|
| |
Searched for them with:
git grep -E '[!=]=.*PIPE_TEXTURE_2D|PIPE_TEXTURE_2D.*[!=]=|case.*PIPE_TEXTURE_2D'
Behavior hasn't been changed.
|
|
|
|
|
|
| |
Plumb the constant buffer sizes down into the tgsi interpreter where
we can do bounds checking. Optional debug code warns upon out-of-bounds
reading. Plus add a few other assertions in the TGSI interpreter.
|
|
|
|
| |
This fixes fdo bug #29286.
|
|
|
|
|
|
|
| |
That is, remove pipe_context::draw_arrays, pipe_context::draw_elements,
pipe_context::draw_arrays_instanced,
pipe_context::draw_elements_instanced,
pipe_context::draw_range_elements.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some drivers define a generic function that is called by all drawing
functions. To implement draw_vbo for such drivers, either draw_vbo
calls the generic function or the prototype of the generic function is
changed to match draw_vbo.
Other drivers have no such generic function. draw_vbo is implemented by
calling either draw_arrays and draw_elements.
For most drivers, set_index_buffer does not mark the state dirty for
tracking. Instead, the index buffer state is emitted whenever draw_vbo
is called, just like the case with draw_elements. It surely can be
improved.
|
| |
|
| |
|
|
|
|
|
|
| |
And remove checks of surface depth bits. The state tracker should
not turn on depth/stencil testing if the framebuffer doesn't have
depth/stencil.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Need to pass the index indicating which blend terms to use, not which
color buffer we're blending into.
Rename the parameter to blend_quad() and add comments to be more clear
about this.
|
| |
|
|
|
|
|
|
| |
laying down the foundation for everything and implementing most of the
stuff.
linking, gl_VerticesIn and multidimensional inputs are left.
|
| |
|
| |
|
|
|
|
|
|
| |
allows application to not only request the frequency of the TIME_ELAPSED
clock but also to detect if that frequency was consistent throughout the
entire bracketed range of graphics commands.
|
|
|
|
| |
to figure out if gpu is finished with all of the previously issues commands
|
|
|
|
|
| |
register masks, multiple output buffers, multiple primitives,
non-linear vertices (elts) and stride semantics.
|
| |
|
| |
|
| |
|
|
|
|
| |
spotted by Vinson
|
| |
|
| |
|
| |
|
|
|
|
| |
we need to change it to support composite types
|
|
|
|
| |
Brian spotted those
|
| |
|
| |
|
|
|
|
|
|
|
| |
interface wise we have everything needed by d3d10 and gl transform feedback.
the draw module misses implementation of some corner cases (e.g. when stream
output wants different number of components per output than normal rendering
paths)
|
|
|
|
| |
aka transform feedback
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This passes on r300g, the only bit I'm not really sure about is the handling
of the sampler_view in st_atom_texture.c, I unreference it there if the swizzle
value changes and I also have to create a new set of functions to create a new
one since the u_sampler.c ones don't handle swizzle so much.
adds r300g + softpipe enables, I think other drivers could pass easily enough.
Signed-off-by: Dave Airlie <[email protected]>
|
|\
| |
| |
| |
| | |
Conflicts:
src/gallium/state_trackers/python/p_context.i
|
| | |
|
|/
|
|
| |
Fixes regression from commit f2e05acac931889e0820e1cc5d7ea810048a6b5f.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
src/mesa/state_tracker/st_gen_mipmap.c
src/mesa/state_tracker/st_texture.c
|
| |
| |
| |
| |
| |
| |
| |
| | |
prevents segfault when state trackers try to set default mask.
Other option would be to make this required only for drivers
supporting multisampling, but this seems more clean.
Only dummy implementations (for normal drivers) provided (no driver
supports multisampling yet neither).
|
| | |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Use front/back instead of cw/ccw throughout.
Also, use offset_point/line/fill instead of offset_cw/ccw.
Brings gallium representation of this state into line with its main
user, and also what turns out to be the most common hardware
representation.
This fixes a long-standing bias in the interface towards the
architecture of the software rasterizer.
|
| | | |
|
|/ /
| |
| |
| | |
Signed-off-by: Corbin Simpson <[email protected]>
|
| | |
|
| | |
|