| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Without this, apps/tests that tried to use a DXT/sRGB format would die on
a failed assertion (st_texture.c:80).
|
|
|
|
|
|
| |
Only the XYZ components are checked to be negative by SVGA3DOP_TEXKILL.
GL_ARB_fp requires all four components be checked. Emit a second texkill
for W if needed.
|
|
|
|
|
|
|
| |
We only need to do the divide by Q step for TXP instructions.
This fixes the incorrectly rendered soft shadow test in Lightsmark.
Along with the previous texture swizzle commit, this also fixes all
the piglit glsl-fs-shadow2d-XX.shader_test failures.
|
|
|
|
|
|
|
| |
This exposes the GL_EXT_texture_swizzle extension and allows the various
depth texture modes to be implemented properly. This, plus a follow-on
texture/shadow change fixes quite a few piglit GLSL shadow sampler test
failures.
|
| |
|
|
|
|
|
|
| |
Emit the SVGA3D_RS_POINTSPRITEENABLE render state.
When sprite_coord_mode=PIPE_SPRITE_COORD_LOWER_LEFT emit extra frag
shader code to invert the Y coordinate of the incoming texcoord.
|
| |
|
|
|
|
| |
See bug 688394
|
|
|
|
|
|
| |
Accurately describe what operations are supported when a format caps
entry is not advertised by the host, and which formats are never
supported, instead of making ad-hoc and often incorrect assumptions.
|
|
|
|
|
|
|
| |
sampled from.
Mitigates issues with hosts where support for these new depth formats is
flaky.
|
| |
|
| |
|
| |
|
|
|
|
| |
TODO: Can we pass this as the same texcoord as fog?
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
HWv8 feature.
Tested with GoogleEarth, Mesa demos.
|
| |
|
| |
|
| |
|
|
|
|
| |
See bug 688383
|
|
|
|
|
|
|
|
|
|
| |
The pipe_sampler_view::format field should be prefered over the resource/
texture format. The former is used to override the texture format for
sRGB decode enable/disable, etc.
Also, use new util_format_is_srgb() helper to catch all sRGB formats.
This fixes the piglit tex-srgb test for GL_EXT_texture_sRGB_decode.
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a regression from a8cf4b6acf9ee996090cc0bb95fa3558b481108c
The problem occured when two successive glDrawArrays calls accessed
subsequent elements in user-space arrays. The user-space array
from the first call wasn't being grown to accomodate the second
draw call's elements.
Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This moves the gallium interface for clears from using a pointer to 4 floats to a pointer to a union of float/unsigned/int values.
Notes:
1. the value is opaque.
2. only when the value is used should it be interpretered according to
the surface format it is going to be used with.
3. float clears on integer buffers and vice-versa are undefined.
v2: fixed up vega and graw, dropped hunks that shouldn't have been in
patch.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
|
|
|
| |
Quickly tested with VMWare Workstation 7.1.4 on Linux with GeForce
GT220. SurfaceFlinger (the display server and compositor) works. 2D
apps with RGB visual works. However, due to missing
PIPE_FORMAT_R8G8B8A8_UNORM support, those with RGBA visual do not.
|
|
|
|
|
| |
Factor out C_SOURCES from Makefile to Makefile.sources, and let Makefile
and SConscript share it.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Conflicts:
src/mesa/state_tracker/st_atom_pixeltransfer.c
src/mesa/state_tracker/st_program.c
|
| | |
|
| |
| |
| |
| |
| |
| | |
Instead of always using the first element's size.
This fixes flashing floor on CINEBENCH R10.
|
| |
| |
| |
| |
| |
| |
| |
| | |
If a user-buffer was referenced twice by a draw command, the affected ranges
were uploaded separately, with only the last one being referenced by the
hardware. Make sure we upload only a single range.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We currently always treat contents of user-buffers as volatile so
we don't need to take any particular action when the state tracker
announces that the contents has changed.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
| |
| |
| |
| | |
See preceeding commit for more info.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Viewperf uses some unusual vertex arrays where the stride is less
than the element size. In this case, the stride was 4 while the
element size was 12. The difference of 8 bytes causes us to miss
uploading the tail bit of the array data.
Typically the stride is >= the element size so there was no problem
with other apps.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Stream user buffer contents rather than trying to maintain persistent
host / hardware copies.
Resulting negative array offsets are not allowed by the hardware,
(well, at least not according to header files), so adjust index bias
to make all array offsets positive.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
| |
| |
| |
| |
| |
| | |
This enables us to pack more data into single upload buffers.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|/
|
|
|
| |
Also, only flush when going from HW TNL to SW TNL, given it is impossible
for the buffers resulting from SWTNL to be ever referred by HW TNL path.
|
| |
|
|
|
|
| |
User-defined clip planes were a swtnl fallback before.
|
|
|
|
|
| |
This is safe because it's initialized if buffers & PIPE_CLEAR_COLOR and
probably doesn't have any effect otherwise.
|
|
|
|
|
|
| |
Just to keep drivers working.
Reviewed-by: Jakob Bornecrantz <jakob@vmware.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The earlier change to ensure rendertargets and textures are always
rebound at every command buffer start had the downside of making
successive flushes no longer no-ops, as a command buffer with merely
the rebinding commands were being unnecessarily sent to the vGPU.
This change only re-emits the bindings when necessary, by keeping track
of the need to rebind outside of the dirty state update mechanism.
|
| |
|
| |
|