| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
compiles. Might need to do something to make it possible to save/restore
stencil ref.
|
| |
|
| |
|
| |
|
|
|
|
| |
Also fix and clarify depth/stencil/alpha documentation a bit.
|
|
|
|
|
| |
More consistent with other state data, might allow some compilers to pack
the struct better (doesn't matter for gcc).
|
|
|
|
|
|
|
|
| |
This will make driver's life a bit harder, however it makes sense that stencil
reference value is not part of the pipe_depth_stencil_alpha_state, because
it often (there are some algorithms which require this) changes more frequently
than the rest of the dsa state. This is also encouraged by some graphic APIs.
Treat it similar to pipe_blend_color.
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/drivers/nv10/nv10_state.c
src/gallium/drivers/nv20/nv20_state.c
src/gallium/drivers/nv50/nv50_program.c
|
| | |
|
| |
| |
| |
| |
| | |
This determines if points should be rasterized according to GL point rules
or as normal quads (GL point sprites / d3d points / d3d point sprites).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The point size min/max registers (unused by mesa state tracker) were removed
since most hardware couldn't do much with them. However, we don't want to have
to rely on hw to do point size clamping correctly to implementation
dependent limits, hence have to do that in the vertex shader. This should also
solve a potential problem with (non-AA) points smaller than 1.0 which according
to OGL still have size 1.0.
Note that OGL point rendering is odd, in particular point sprites are rasterized
differently to points. Some hardware might support those different modes, but in
any case the different clamping values used for smooth/multisampled/sprite
enabled points might help a bit for hw which rasterizes points the same as point
sprites.
Also tweak mesa's ff to vertex shader translation so don't have to clamp twice in
case of point attenuation.
|
| |
| |
| |
| | |
there was some confusion between point size state and point size output.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't need sprite coord origin per coord.
Also, don't need separate sprite enable bit - if all coords have it diabled,
then there are no point sprites (technically, there's a distinction in pre-GL3,
but it only differs in having more leniency in clamping to max size, something
the state tracker would need to handle and the hardware won't bother anyway).
Also, use packed field for the per-coord enables.
All in all, should save 3 dwords in rasterizer state (from 10 down to 7).
|
| |
| |
| |
| |
| |
| |
| | |
The state tracker is responsible for clamping to any graphics API enforced
size min/max limits for both the static point_size setting as well as per
vertex point size (in the vertex shader).
Note that mesa state tracker didn't actually use these values.
|
| |
| |
| |
| | |
(cherry picked from commit 0371956d66cdc8a1629753fca9cb3cdc49b0d145)
|
| |
| |
| |
| | |
Signed-off-by: José Fonseca <[email protected]>
|
| |
| |
| |
| |
| |
| | |
The .o.c rule is consider obsolete.
Signed-off-by: José Fonseca <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: José Fonseca <[email protected]>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Leftover that was never used in this driver
|
| | |
|
| |
| |
| |
| | |
Argh, forgot to commit this fix before pushing.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Cylinder wrap mode works with perspective interpolation now.
|
| | |
|
| |
| |
| |
| | |
This reverts commit 444cd62ca33a45bd39e8408979a0a01c246c6381.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the texture priority field is 0.125 set the PROG_PARAM_BIT_CYL_WRAP
flag. The gallium state tracker will look for this flag.
This feature is only for testing purposes and may be remove at some
point. But if it's useful we could write a GL/Mesa extension to
expose it properly.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Allows one to declare fragment shader inputs with cylindrical wrap info.
|
| | |
|
| |
| |
| |
| | |
Little utility after development stabilisation, use tgsi_dump instead.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This object can be shared with another context, so we cannot just
delete it when the owning context is being destroyed.
Ensuring that buffer objects are properly refcounted guarantees
NullBufferObj is destroyed when all references to it are removed.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Lets see if this is not too pedantic. Obj pointers are never exposed to
GL apps so it should be possible to get this right.
Furthermore apps with GL widgets and test suits create and destroy many
contexts and objects, so bad reference counting is not really an option.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Always use _mesa_reference_buffer_object, and never call
ctx->Driver.DeleteBuffer() directly to prevent dangling pointers to the
null buffer object.
This fixes crash/assertions in sharedtex_mt and Autodesk Mudbox.
|
| | |
|
| | |
|