summaryrefslogtreecommitdiff
path: root/src/mesa
AgeCommit message (Collapse)Author
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: don't send now forbidden register to kernel when with memory managerJerome Glisse
2009-05-14r300: Make sure to drop current hardware state reference to texture objects.Michel Dänzer
Fixes potential texture object leaks.
2009-05-13R1xx/r2xx: Don't use an alpha texture format for GLX_TEXTURE_FORMAT_RGB_EXTAlex Deucher
In r*00SetTexBuffer2(), if the passed in text glx_texture_format is GLX_TEXTURE_FORMAT_RGB_EXT, then we should use an RGB-only texture format, even if the DRI buffer has four channels. https://bugs.freedesktop.org/show_bug.cgi?id=21609
2009-05-13radeon: Don't crash generating mipmaps when pixels=NULLOwen W. Taylor
When a NULL value of pixels is passed to TexImage2D and SGIS_generate_mipmap is enabled, don't try to generate the mipmap tree: we don't have data yet for the texture and will crash. https://bugs.freedesktop.org/show_bug.cgi?id=21648
2009-05-13Don't use an alpha texture format for GLX_TEXTURE_FORMAT_RGB_EXTOwen W. Taylor
In r300SetTexBuffer2(), if the passed in text glx_texture_format is GLX_TEXTURE_FORMAT_RGB_EXT, then we should use an RGB-only texture format, even if the DRI buffer has four channels. https://bugs.freedesktop.org/show_bug.cgi?id=21609
2009-05-13Call _mesa_update_stencil() before accessing ctx->Stencil._EnabledOwen W. Taylor
ctx->Stencil._Enabled is derived state and not immediately updated when the stencil parameters are changed; we need to make sure that it is up-to-date before accessing it. https://bugs.freedesktop.org/show_bug.cgi?id=21608
2009-05-13Remove subpixel offset from viewportOwen W. Taylor
Remove an eigth-pixel offset of the viewport inherited from R100 code. This seems not to be necessary and causes blurring when sampling textures 1:1. https://bugs.freedesktop.org/show_bug.cgi?id=20340
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-13st/mesa: enable GL_APPLE_vertex_array_object for gallium driversBrian Paul
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-13mesa: delete array objects before buffer objects during context tear-downBrian Paul
The former may point to the later.
2009-05-13mesa: clean-up vertex array object VBO unbinding and delete/refcountingBrian Paul
Don't really delete vertex array objects until the refcount hits zero. At that time, unbind any pointers to VBOs. (cherry picked from commit 32b851c80792623195069d7a41a5808cff3b2f6f)
2009-05-13mesa: reference counting for gl_array_objectBrian Paul
Every kind of object that can be shared by multiple contexts should be refcounted. (cherry picked from commit 1030bf0ded2a88a5e27f7a4d393c11cfde3d3c5a)
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-12swrast: update/restore the opt_sample_rgb/rgba_2d() functionsBrian Paul
2009-05-12radeon: glReadBuffer set _NEW_BUFFERS, not _NEW_PIXELJerome Glisse
This was broken with last merge see 62043b27575c378c027251316421e4699f461108 for explanations
2009-05-12r300/r500: make sure we detect constant buffer changesJerome Glisse
This was broken with last merge see f48473e42511f8d37a239a07f791bc0a87209e5b for explanations.
2009-05-12radeon: avoid segfault in radeon_update_renderbuffers() if using DRI1Tormod Volden
Basically the same as 43d9020ff1e975e7f4f9480d9ef24f0b9fb2141f for intel. Bug 21688. Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
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-11Merge branch 'mesa_7_5_branch'Brian Paul
Conflicts: Makefile src/mesa/main/version.h
2009-05-11st: do proper refcounting for framebuffer surfacesBrian Paul
2009-05-11mesa: updated comments for _mesa_generate_mipmap()Brian Paul
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-11mesa: better handling/printing of driver-specific opcodes, register filesBrian Paul
Drivers such as i965 define extra instruction opcodes and register files. Improve the program printing code to handle those opcodes/files better.
2009-05-11mesa: Fixed a texture memory leakBrian Paul
The current texture for any particular texture unit is given an additional reference in update_texture_state(); but if the context is closed before that texture can be released (which is quite frequent in normal use, unless a program unbinds and deletes the texture and renders without it to force a call to update_texture_state(), the memory is lost. This affects general Mesa; but the i965 is particularly affected because it allocates a considerable amount of additional memory for each allocated texture. (cherry picked from master, commit c230767d6956b63a2b101acb48f98823bb5dd31a)
2009-05-10radeon: add support for new dri2 interfaces & fix single buffer renderingJoel Bosveld
2009-05-10Merge commit 'origin/master' into radeon-rewriteJerome Glisse
Conflicts: src/mesa/drivers/dri/r200/r200_state.c src/mesa/drivers/dri/r300/r300_context.h src/mesa/drivers/dri/r300/r300_fragprog.c src/mesa/drivers/dri/r300/r300_state.c src/mesa/drivers/dri/r300/r300_texmem.c src/mesa/drivers/dri/r300/r300_texstate.c src/mesa/drivers/dri/r300/r500_fragprog.c src/mesa/drivers/dri/radeon/radeon_screen.c src/mesa/drivers/dri/radeon/radeon_state.c
2009-05-09radeon: don't include cs uncondionalyJerome Glisse
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-08mesa: Fixed a texture memory leakRobert Ellison
The current texture for any particular texture unit is given an additional reference in update_texture_state(); but if the context is closed before that texture can be released (which is quite frequent in normal use, unless a program unbinds and deletes the texture and renders without it to force a call to update_texture_state(), the memory is lost. This affects general Mesa; but the i965 is particularly affected because it allocates a considerable amount of additional memory for each allocated texture.
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-08mesa: set version to 7.5-rc1Brian Paul
2009-05-08i965: const qualifiersBrian Paul
2009-05-08mesa: raise MAX_VARYING (number of shader varying vars) to 16Brian Paul
16 is the limit for now because of various 32-bit bitfields.
2009-05-08mesa: assertions to check for too many vertex outputs or fragment inputsBrian Paul
2009-05-08glsl: check number of varying variables against the limitBrian Paul
Link fails if too many varying vars.
2009-05-08mesa: issue warning for out of bounds array indexesBrian Paul
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-24 15:43:58 +0000