| Age | Commit message (Collapse) | Author |
|---|
|
Oh, look, GLSL instructions. I wonder what I'll do next.
|
|
Oh, look, it's more features. :3
|
|
HW trig does a premultiply by 2pi, where Mesa does another premultiply by pi.
This is a problem.
|
|
|
|
See the previous commit for an explanation. This is just all the support code
for GB_TILE_CONFIG.
|
|
This accompanies kernel patches that make GB_TILE_CONFIG's various members
completely controlled in DRM.
GB_TILE_CONFIG has the following controls:
- The number of GB (pixel) pipes enabled
- The size and style of tiling
- Subpixel precision (either 1/12 or 1/16)
Per airlied and glisse, userspace and kernel will now agree (always) on
a subpixel precision of 1/12, and tiling will always be kernel-controlled.
|
|
GA_ENHANCE is now the kernel's problem.
|
|
Lops work fine as long as HW TCL is off. (I think I know why.)
|
|
Per agd5f.
|
|
Makes the last three commits suck much less. :3
|
|
Should work, but doesn't. Hm.
|
|
Those parts are nearly solid compared to the shaders.
|
|
|
|
Odds are good that we'll die later anyway, so we might as well do it before
we start dancing on random memory.
|
|
Even though we *can* render 10,000-pixel-wide lines, let's not advertise it.
|
|
Anisotropic filtering should work, and OQ is broken.
|
|
Compile-tested only, sorry.
|
|
|
|
BEGIN/END_CS pair, a few asserts, and a slightly more correct VTE setup.
|
|
Drivers can just keep track of whether they are within a query
by monitoring the begin/end query callbacks. The flag adds no
information beyond that.
Only softpipe was examining this flag -- it has been fixed up
and retested with demos/arbocclude.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead, stash the debug info under the handy debug flag.
Bug #20053
|
|
Both EXT_fbo and ARB_fbo agree on this. Fixes a segfault in the metaops
mipmap generation in Intel for SGIS_generate_mipmap of S3TC textures in
Regnum Online.
Bug #21654.
|
|
|
|
|
|
Bug #21691.
|
|
The _Enabled field isn't updated at the point that DrawBuffers is called,
and the Driver.Enable() function does the testing for stencil buffer
presence anyway.
bug #21608 for Radeon
|
|
The docs actually explain this, but not in a terribly clear manner.
This nearly fixes the piglit cubemap testcase, except that something's
going wrong with the nearest filtering at 2x2 sizes in the testcase.
Looks good by visual inspection, though.
Bug #21692
|
|
I don't have a testcase for this, but it seems clearly wrong.
|
|
Before, if the VP output something that is in the attributes coming into
the WM but which isn't used by the WM, then WM would end up reading subsequent
varyings from the wrong places. This was visible with a GLSL demo
using gl_PointSize in the VS and a varying in the WM, as point size is in
the VUE but not used by the WM. There is now a regression test in piglit,
glsl-unused-varying.
|
|
|
|
This comes from a radeon-rewrite fallback fix, but may also fix stencil
clear failure when the polygon winding mode is flipped.
|
|
|
|
With 1D textures, GL_TEXTURE_WRAP_T should be ignored (only
GL_TEXTURE_WRAP_S should be respected). But the i965 hardware
seems to follow the value of GL_TEXTURE_WRAP_T even when sampling
1D textures.
This fix forces GL_TEXTURE_WRAP_T to be GL_REPEAT whenever 1D
textures are used; this allows the texture to be sampled
correctly, avoiding "imaginary" border elements in the T direction.
This bug was demonstrated in the Piglit tex1d-2dborder test.
With this fix, that test passes.
|
|
One warning message:
drm_i915_getparam: -22
was still being sent to fprintf(). This causes all Piglit tests to fail,
even with MESA_DEBUG=0.
Using _mesa_warning() to emit the message allows the general Mesa controls
for messages like this to be applied.
|
|
|
|
|
|
|
|
Fixes segfault in context tear-down when glClear was never called.
|
|
|
|
No special driver changes are needed for this extension.
|
|
|
|
Conflicts:
src/mesa/main/arrayobj.c
src/mesa/main/arrayobj.h
src/mesa/main/context.c
|
|
gl_array_object encapsulates a set of vertex arrays (see the
GL_APPLE_vertex_array_object extension).
Create a private gl_array_object for drawing the quad for intel_clear_tris()
so we don't have to worry about the user's vertex array state.
This fixes the no-op glClear bug #21638 and removes the need to call
_mesa_PushClientAttrib() and _mesa_PopClientAttrib().
|
|
The former may point to the later.
|
