Age | Commit message (Collapse) | Author |
|
Fixes:
glsl-fs-if-nested-loop.
|
|
Fixes:
glsl1-Negation
glsl1-Negation2
|
|
Need to bring back correct fb write with header to set pixel
write mask. Fallback for now.
|
|
Fix pipe control command for depth stall and PS_DEPTH_COUNT write.
|
|
Need to set point sprite function in fixed SF state now on sandybridge.
|
|
Fix incorrect scissor rect struct and missed scissor state pointer
setting for sandybridge.
|
|
Depth offset function is moved to SF stage on sandybridge.
|
|
|
|
Sandybridge doesn't have Xstart/Ystart in payload header.
|
|
Until we fixed SIMD16 kernel, force to SIMD8 on sandybridge now.
|
|
Must issue a pipe control with any non-zero post sync op before
write cache flush = 1 pipe control.
|
|
|
|
Sandybridge's PS constant buffer payload size is decided from
push const buffer command, incorrect size would cause wrong data
in payload for position and vertex attributes. This fixes coefficients
for tex2d/tex3d.
|
|
Sandybridge has not much change on texture sampler with Ironlake.
|
|
Jump count is for 64bit long each, so one instruction requires 2
like on Ironlake.
|
|
Until conditional instructions were fixed, use SPF mode instead for now.
|
|
|
|
Sandybridge's VF would convert quads to polygon which not required
for GS then. Current GS state still would cause hang on lineloop.
|
|
|
|
|
|
|
|
Don't double store position in vertex attribute. This makes color
interpolation right by using barycentric coordinates.
|
|
Accumulator update flag must be set for implicit update on sandybridge.
|
|
Dump new state object on sandybridge for cc viewport, clip viewport,
depth stencil, cc and blend state.
|
|
|
|
Fixes glsl-algebraic-pow-2 in brw_wm_glsl.c mode.
|
|
Sending down data that doesn't get read doesn't make any sense, and
would make handling things like gl_FrontFacing and gl_PointCoord
harder.
|
|
Things are simpler these days thanks to barycentric interpolation
parameters being handed in in the payload.
|
|
|
|
|
|
|
|
|
|
rc_for_all_reads_src() and rc_pair_for_all_reads_arg() pass references to
instruction sources to the callback so they can be modified directly.
|
|
The driver actually creates a 3D texture aligned to POT and does all
the magic with texture coordinates in the fragment shader. It first
emulates REPEAT and MIRRORED wrap modes in the fragment shader to get
the coordinates into the range [0, 1]. (already done for 2D NPOT)
Then it scales them to get the coordinates of the NPOT subtexture.
NPOT textures are now less of a lie and we can at least display
something meaningful even for the 3D ones.
Supported wrap modes:
- REPEAT
- MIRRORED_REPEAT
- CLAMP_TO_EDGE (NEAREST filtering only)
- MIRROR_CLAMP_TO_EDGE (NEAREST filtering only)
- The behavior of other CLAMP modes is undefined on borders, but they usually
give results very close to CLAMP_TO_EDGE with mirroring working perfectly.
This fixes:
- piglit/fbo-3d
- piglit/tex3d-npot
|
|
Taking the W component from coords directly ignores swizzling. Instead,
take the component which is mapped to W in the TEX instruction parameter.
The same for Z.
NOTE: This is a candidate for the 7.9 branch.
|
|
NOTE: This is a candidate for the 7.9 branch.
|
|
NOTE: This is a candidate for the 7.9 branch.
|
|
Some random stuff I had here.
1) Fixed some misleading comments.
2) Removed fake_npot, since it's redundant.
3) lower_texture_rect -> scale_texcoords
4) Reordered and reindented some TEX transform code.
|
|
Fixes:
glsl-fwidth
glsl-derivs-swizzle
|
|
Fixes:
glsl-fs-all-02
glsl-fs-dot-vec2
|
|
These are generated for scalar operands instead of plain equal/nequal.
But for scalars, they're the same anyway. +30 piglits.
|
|
We'd end up reading some non-x component of the float RHS. +53 piglits.
|
|
Not sure how I managed to get tests to succeed without this. +54 piglits.
|
|
This is already NULL'ed in _mesa_init_driver_functions.
|
|
This is only used in the i915 driver where it provides little benefit
for very few applications that use it with fixed function TNL.
|
|
This extension was never enabled in any driver.
|
|
As per discussions at XDS.
|
|
As per discussions at XDS.
|
|
1. We can't turn an instruction into a presubtract operation if it
writes to one of the registers it reads from.
2. If we turn an instruction into a presubtract operation, we can't
remove that intruction unless all readers can use the presubtract
operation.
This fixes fdo bug 30337.
This is a candidate for the 7.9 branch.
|
|
|