summaryrefslogtreecommitdiff
path: root/src/mesa/drivers
AgeCommit message (Collapse)Author
2009-06-02mesa: plug in new _mesa_CopyBufferSubData() functionsBrian Paul
2009-06-02glapi: regenerated files for GL_ARB_copy_bufferBrian Paul
2009-06-02intel: Clip to window after calling Driver.TexImage2DIan Romanick
This prevents the width / height from being clipped to the window size before the texture is allocated. This matches intelCopyTexImage1D. This should fix bug #21227 Signed-off-by: Ian Romanick <ian.romanick@intel.com>
2009-06-02i915: Don't put VBOs in graphics memory unless required for an operation.Eric Anholt
This saves doing swtnl from uncached memory, which is painful. Improves clutter test-text performance by 10% since it started using VBOs.
2009-06-02i965: Support OPCODE_TRUNC in the brw_wm_fp.c code.Eric Anholt
This gets two more glean glsl1 tests using the non-GLSL path.
2009-06-01Use separate $(MINSTALL) for installing librariesDan Nicholson
The special feature of bin/minstall to copy symlinks is only ever needed when installing libraries which may have .so symlinks. All the headers and directories can use a normal install program. These two modes are separated as $(INSTALL) and $(MINSTALL) to allow the user (or autoconf) to override installing normal files as they please. An autoconf check for the install program has been added and will be used in preference to minstall when available. Fixes bug 16053.
2009-05-26i915: Fall back on NPOT textured metaops on 830-class.Eric Anholt
2009-05-26i915: Restore the Viewport and DepthRange functions on 8xx.Eric Anholt
Fixes failed viewport updates on glxgears (and other apps) resize since e41780fedc2c1f22b43118da30a0103fa68b769f. Bug #20473.
2009-05-26intel: Override MaxRenderbufferSize with hardware constraintsChris Wilson
Limit the maximum renderbuffer size to 8192 on i965 and to 2048 on earlier hardware.
2009-05-21i965: fix whitespace in brw_tex_layout.cEric Anholt
The broken indentation was driving me crazy, so fix other stuff while I'm here.
2009-05-21i956: Make state dependency of SF on drawbuffer bounds match Mesa's.Eric Anholt
Noticed while debugging a weird 1D FBO testcase that left its existing viewport and projection matrix in place when switching drawbuffers. Didn't fix the testcase, though.
2009-05-21intel: Fall back on any rendering to texture with no miptree.Eric Anholt
Fixes segfault on an fbo.c negative test for FBO with texture width/height of 0. Previously we just tested for border != 0 to work around this segfault.
2009-05-21intel: Mark the FBO as incomplete if there's no intel_renderbuffer for it.Eric Anholt
This happens to rendering with textures with a border, which had resulted in a segfault on dereferencing the irb.
2009-05-21intel: Don't segfault on glGenerateMipmaps of a cube map with one face defined.Eric Anholt
This presumably applies to SGIS_generate_mipmaps as well.
2009-05-21intel: Use _mesa_CheckFramebufferStatusEXT insteaad of glCheck...Eric Anholt
Fixes a segfault in our oglconform fbo test.
2009-05-21i965: rename var: s/tmp/vs_inputs/Brian Paul
2009-05-18Merge branch 'mesa_7_5_branch'Brian Paul
Conflicts: Makefile src/mesa/main/version.h
2009-05-15intel: Don't complain on falling back from PBO fastpaths.Eric Anholt
Instead, stash the debug info under the handy debug flag. Bug #20053
2009-05-15i915: Fix 945 cube map layout for the small mipmaps along the bottom.Steinar H. Gunderson
Bug #21691.
2009-05-15i915: Use Stencil.Enabled instead of Stencil._Enabled in DrawBuffers.Eric Anholt
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
2009-05-15i915: Only use the new 945 cube layout for compressed textures.Eric Anholt
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
2009-05-14i965: Fix varying payload reg assignment for the non-GLSL-instructions path.Eric Anholt
I don't have a testcase for this, but it seems clearly wrong.
2009-05-14i965: Fix register allocation of GLSL fp inputs.Eric Anholt
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.
2009-05-14intel: Use FRONT_AND_BACK for StencilOp as well.Eric Anholt
2009-05-14intel: Use GL_FRONT_AND_BACK for stencil clearing.Eric Anholt
This comes from a radeon-rewrite fallback fix, but may also fix stencil clear failure when the polygon winding mode is flipped.
2009-05-14i965: fix 1D texture borders with GL_CLAMP_TO_BORDERRobert Ellison
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.
2009-05-14i965: send all warnings through _mesa_warning()Robert Ellison
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.
2009-05-14r300: Make sure to drop current hardware state reference to texture objects.Michel Dänzer
Fixes potential texture object leaks.
2009-05-13Merge branch 'mesa_7_5_branch'Brian Paul
2009-05-13intel: added null ptr checkBrian Paul
Fixes segfault in context tear-down when glClear was never called.
2009-05-13intel: enable GL_APPLE_vertex_array_objectBrian Paul
No special driver changes are needed for this extension.
2009-05-13Merge branch 'mesa_7_5_branch'Brian Paul
Conflicts: src/mesa/main/arrayobj.c src/mesa/main/arrayobj.h src/mesa/main/context.c
2009-05-13intel: create a private gl_array_object for intel_clear_tris(), fix bug 21638Brian Paul
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().
2009-05-12i965: enable additional code in emit_fb_write()Brian Paul
Not 100% sure this is right, but the invalid assertion is fixed...
2009-05-12i965: increase BRW_EU_MAX_INSNBrian Paul
2009-05-12i965: commentBrian Paul
2009-05-12intel: Skip the DRI2 renderbuffer update when doing Viewport on an FBO.Eric Anholt
2009-05-12intel: Map write-only buffer objects through the GTT when possible.Eric Anholt
This looks to be a win of a few percent in cairogears with new vbo code, thanks to not polluting caches.
2009-05-12i915: Fix driver after HW glGenerateMipmap commit.Eric Anholt
2009-05-11Test either GL_FRONT_LEFT or GL_FRONT for front-buffer renderingIan Romanick
For non-stereo visuals, which is all we support, we treat GL_FRONT_LEFT as GL_FRONT. However, they are technically different, and they have different enum values. Test for either one to determine if we're in front-buffer rendering mode. This fix was suggested by Pierre Willenbrock. Signed-off-by: Ian Romanick <ian.d.romanick@intel.com> (cherry picked from commit 2085cf24628be7cd297ab0f9ef5ce02bd5a006e2)
2009-05-11i965: handle extended swizzle terms (0,1) in get_src_reg()Brian Paul
Fixes failed assertion in progs/glsl/twoside.c (but still wrong rendering).
2009-05-08i965: improve debug loggingRobert Ellison
Looking for memory leaks that were causing crashes in my environment in a situation where valgrind would not work, I ended up improving the i965 debug traces so I could better see where the memory was being allocated and where it was going, in the regions and miptrees code, and in the state caches. These traces were specific enough that external scripts could determine what elements were not being released, and where the memory leaks were. I also ended up creating my own backtrace code in intel_regions.c, to determine exactly where regions were being allocated and for what, since valgrind wasn't working. Because it was useful, I left it in, but disabled and compiled out. It can be activated by changing a flag at the top of the file.
2009-05-08i965: fix memory leak in context/renderbuffer region managementRobert Ellison
A temporary change to the intelMakeCurrent() function to make it work with frame buffer objects causes the static regions associated with the context (the front_region, back_region, and depth_region) to take on an additional reference, with no corresponding release. This causes a memory leak if a program repeatedly creates and destroys contexts. The fix is the corresponding hack, to unreference these regions when the context is deleted, but only if the framebuffer objects are still present and the same regions are still referenced within. Both sets of code have comment blocks referring to each other.
2009-05-08i965: fix segfault on low memory conditionsRobert Ellison
When out of memory (in at least one case, triggered by a longrunning memory leak), this code will segfault and crash. By checking for the out-of-memory condition, the system can continue, and will report the out-of-memory error later, a much preferable outcome.
2009-05-08intel: Add a metaops version of glGenerateMipmapEXT/SGIS_generate_mipmaps.Eric Anholt
In addition to being HW accelerated, it avoids the incorrect (black) rendering of the mipmaps that SW was doing in fbo-generatemipmap. Improves the performance of the mipmap generation and drawing in fbo-generatemipmap by 30%.
2009-05-08intel: Put the constant texcoords used in metaops into a vbo.Eric Anholt
Make this be its own function for setup/teardown of the binding of these texcoords. No performance difference in the engine demo (I just felt dirty not using a VBO for this), and I think it should be more resilient to interference from current GL state.
2009-05-08i965: const qualifiersBrian Paul
2009-05-08i965: don't use GRF regs 126,127 for WM programsBrian Paul
They seem to be used for something else and using them for shader temps seems to lead to GPU lock-ups. Call _mesa_warning() when we run out of temps. Also, clean up some debug code.
2009-05-07i965: relAddr local var (to make debug/test a little easier)Brian Paul
2009-05-06i965: Remove bad constant buffer constant-reg-already-loaded optimization.Eric Anholt
Thanks to branching, the state of c->current_const[i].index at the point of emitting constant loads for this instruction may not match the actual constant currently loaded in the reg at runtime. Fixes a regression in my GLSL program for idr's class since b58b3a786aa38dcc9d72144c2cc691151e46e3d5.