summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* i915: Restore the Viewport and DepthRange functions on 8xx.Eric Anholt2009-06-171-0/+21
| | | | | | | | Fixes failed viewport updates on glxgears (and other apps) resize since e41780fedc2c1f22b43118da30a0103fa68b769f. Bug #20473. (cherry picked from commit 0e83e8f51af07a3066519f169f07d9afbf23252e)
* i956: Make state dependency of SF on drawbuffer bounds match Mesa's.Eric Anholt2009-06-171-2/+5
| | | | | | | 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. (cherry picked from commit 3a521d84ecc646fcc65fa3fe7c5f1fdbdebe8bc2)
* intel: Don't complain on falling back from PBO fastpaths.Eric Anholt2009-06-171-3/+3
| | | | | | | Instead, stash the debug info under the handy debug flag. Bug #20053 (cherry picked from commit 22690482e692cb5ed2f84d3e69545c09292e3484)
* mesa: Mark FBOs with compressed color attachments as FBO-incomplete.Eric Anholt2009-06-171-0/+5
| | | | | | | | | 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. (cherry picked from commit 0307e609aa3e707eeb40051bd664d36f2340ba9b)
* i915: Use Stencil.Enabled instead of Stencil._Enabled in DrawBuffers.Eric Anholt2009-06-171-1/+1
| | | | | | | | | 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 (cherry picked from commit 4c6f82989983eecc0b3b724716cb3bcb675664c5)
* i915: Only use the new 945 cube layout for compressed textures.Eric Anholt2009-06-171-1/+4
| | | | | | | | | | 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 (cherry picked from commit 5c5a46884899ea25cdf25545d6ab3d9a74eafa3a)
* i965: Fix varying payload reg assignment for the non-GLSL-instructions path.Eric Anholt2009-06-171-8/+10
| | | | | I don't have a testcase for this, but it seems clearly wrong. (cherry picked from commit dc657f3929fbe03275b3fae4ef84f02e74b51114)
* i965: Fix register allocation of GLSL fp inputs.Eric Anholt2009-06-174-13/+27
| | | | | | | | | | | 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. (cherry picked from commit 0f5113deed91611ecdda6596542530b1849bb161)
* intel: Use FRONT_AND_BACK for StencilOp as well.Eric Anholt2009-06-171-1/+2
| | | | (cherry picked from commit 64980125c76b05501a6fe7fe20fe52438f459129)
* intel: Use GL_FRONT_AND_BACK for stencil clearing.Eric Anholt2009-06-171-1/+2
| | | | | | This comes from a radeon-rewrite fallback fix, but may also fix stencil clear failure when the polygon winding mode is flipped. (cherry picked from commit d866abeffc7e4a29736fa35fb8ac09c3a28a44d6)
* intel: Skip the DRI2 renderbuffer update when doing Viewport on an FBO.Eric Anholt2009-06-171-1/+1
| | | | (cherry picked from commit d4a42b0ce6455d03be70aa56aacd779be193aca4)
* intel: Map write-only buffer objects through the GTT when possible.Eric Anholt2009-06-172-2/+15
| | | | | | This looks to be a win of a few percent in cairogears with new vbo code, thanks to not polluting caches. (cherry picked from commit aa422b262509bc0763a50f63a51a1730139ea52f)
* mesa: rework viewport/scissor initialization codeBrian Paul2009-06-175-34/+38
| | | | | | | | | | The first time a context is bound to a drawable, the viewport and scissor bounds are initialized to the buffer's size. This is actually a bit tricky. A new _mesa_check_init_viewport() function is called in several places to check if the viewport has been initialized. We also use a new ctx->ViewportInitialized flag instead of the overloaded ctx->FirstTimeCurrent flag.
* mesa: added null ptr check in Fake_glXCreatePixmap()Brian Paul2009-06-171-1/+1
| | | | Fixes segfault in progs/xdemos/glxgears_pixmap.c
* st/glx: added null ptr check in Fake_glXCreatePixmap()Brian Paul2009-06-171-1/+1
| | | | Fixes segfault in progs/xdemos/glxgears_pixmap.c
* Revert "scons: Debug build by default."José Fonseca2009-06-172-2/+2
| | | | | | Per Brian's request. This reverts commit 25f0c33bb3509958a532bdd72b3945c1d5d1cad5.
* progs/wgl: Fix shreadtex_mt too.José Fonseca2009-06-171-6/+24
|
* progs/wgl: Tweak the initialization wait in wglthreads.José Fonseca2009-06-171-2/+2
| | | | There was still a non-zero probability for wglShareLists of failing.
* progs/wgl: Get wglShareLists working in wglthreads.José Fonseca2009-06-171-6/+23
| | | | | | | wglShareLists is a little picky -- it seems to check if it has exclusive access to a lock, and fails if it doesn't. This allows the texture to be shared with all windows.
* scons: Debug build by default.José Fonseca2009-06-172-2/+2
| | | | Match what autotools and other build systems do by default.
* GLX: attempt to fix glean makeCurrent test cases.Brian Paul2009-06-172-2/+6
| | | | | | | | | | | | | Two parts to this: One we don't keep pointers to possibly freed memory anymore once we unbind the drawables from the context. Brian I need to figure out what the comment you made there, can we get a glean/piglit test so we can fix it properly? If the new gc is the same as the oldGC, we call the unbind even though we just bound it in that function. doh. (cherry picked from master, commit 77506dac8e81e9548a7e9680ce367175fe5747af)
* docs: Document building with SCons.José Fonseca2009-06-171-2/+50
|
* wgl: Factor out some repetitive code into inline functions.José Fonseca2009-06-171-29/+28
|
* progs/wgl: Allow resizing wglthreads' windows.José Fonseca2009-06-171-1/+1
|
* i965: fix bugs in projective texture coordinatesBrian Paul2009-06-165-20/+54
| | | | | | | | | | | | | | | | | | | | | | | | For the TXP instruction we check if the texcoord is really a 4-component atttibute which requires the divide by W step. This check involved the projtex_mask field. However, the projtex_mask field was being miscalculated because of some confusion between vertex program outputs and fragment program inputs. 1. Rework the size_masks calculation so we correctly set bits corresponding to fragment program input attributes. 2. Rename projtex_mask to proj_attrib_mask since we're interested in more than just texcoords (generic varying vars too). 3. Simply the indexing of the size_masks and proj_attrib_mask fields. 4. The tracker::active[] array was mis-dimensioned. Use MAX_PROGRAM_TEMPS instead of a magic number. 5. Update comments, add new assertions. With these changes the Lightsmark demo/benchmark renders correctly, until we eventually hit a GPU lockup...
* softpipe: fix out of bounds quad rasterization bugBrian Paul2009-06-161-3/+6
| | | | | | | | For some triangles we can generate quads which lie just outside the surface bounds. Just check the quad's mask before trying to emit/process the quad. Fixes failed assertion in Lightsmark.
* mesa: fix incorrect viewport clamping in _mesa_set_viewport()Brian Paul2009-06-161-2/+2
| | | | | A 0 by 0 viewport size is legal. Don't clamp against lower bound of one. The error checking earlier in the function prevents negative values.
* mesa: fix REMAINDER() macroBrian Paul2009-06-161-1/+1
| | | | | The results were incorrect for some negative values of A. See bug 21872.
* gallium: Avoid atomic ops / locking when src is dst.José Fonseca2009-06-161-14/+14
|
* progs/wgl: Quit after displaying usage for -h option.José Fonseca2009-06-161-0/+1
|
* progs/wgl: Use appropriate types to silence msvc warnings.José Fonseca2009-06-161-7/+7
|
* progs/wgl: Fix assertion failure in wglthreads' texture creation.José Fonseca2009-06-161-8/+10
|
* intel: Release fb backing regions in intelDestroyBuffer()Shuang He2009-06-151-0/+24
| | | | Fixes memory leak when destroying framebuffers.
* python/tests: Add is_depth_stencil_format utility function.José Fonseca2009-06-151-0/+8
|
* python/tests: Cleanup texture_sample.José Fonseca2009-06-151-18/+32
|
* mesa: Always return a value.José Fonseca2009-06-151-0/+1
|
* mesa: Use appropriate float/integer types.José Fonseca2009-06-152-3/+3
|
* mesa: Use type modifier for float constants.José Fonseca2009-06-153-21/+21
|
* mesa: Use integer type with appropriate sign.José Fonseca2009-06-152-4/+4
|
* rtasm: Use 32bit constant.José Fonseca2009-06-151-3/+3
| | | | As we're only using 32bit bitmasks.
* gallium: Ensure assert macro is defined before being used in p_thread.hJosé Fonseca2009-06-151-0/+1
|
* softpipe: Fix softpipe_is_texture_referenced.José Fonseca2009-06-154-0/+22
| | | | | | | | | Render results are only visible when the render cache is flushed. softpipe_is_texture_referenced must reflect that or transfers to/from the textures bound in the framebuffer won't be proceeded of the necessary flush, causing transfer data to be outdated/clobbered. This fixes conform drawpix test with softpipe.
* progs/tests: Use opaque colors.José Fonseca2009-06-151-2/+2
| | | | | Transparency is not relevant for this example, and leads to distraction due to different results in alpha visuals, when capturing images to disk.
* dri st: Don't require the PIPE_TEXTURE_USAGE_RENDER_TARGET property for ↵Thomas Hellstrom2009-06-151-2/+0
| | | | | | depth- and stencil renderbuffers. Signed-off-by: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
* gallium: Fix segfault and valgrind error introduced with commit ↵Thomas Hellstrom2009-06-151-1/+5
| | | | | | 3f2e006b759705abd7c409d30f9aeb1f2a75b83f Signed-off-by: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
* demos: update fbotexture.c to use EXT or ARB functions exclusivelyBrian Paul2009-06-122-38/+77
| | | | | | | | | When the -arb option is specified we use GL_ARB_framebuffer_object intead of GL_EXT_framebuffer_object. For some vendors' OpenGL it's important to call the ARB entrypoints instead of the EXT entrypoints to get correct behaviour. Use some function pointer tricks to do this (instead of GLEW).
* util: additional function pointersBrian Paul2009-06-121-0/+101
|
* mesa: Enable uploads of only depth to z24s8 texturesJakob Bornecrantz2009-06-121-3/+36
|
* mesa: rework vertex shader output / fragment shader input attribute matchingBrian Paul2009-06-111-20/+33
| | | | | | | | | | | | | | | | | | | | Before, if a vertex shader's outputs didn't exactly match a fragment shader's inputs we could wind up with invalid TGSI shader declarations. For example: Before patch: DCL OUT[0], POSITION DCL OUT[1], COLOR[1] DCL OUT[2], GENERIC[0] DCL OUT[3], GENERIC[0] <- note duplicate [0] DCL OUT[4], GENERIC[2] After patch: DCL OUT[0], POSITION DCL OUT[1], COLOR[1] DCL OUT[2], GENERIC[0] DCL OUT[3], GENERIC[1] DCL OUT[4], GENERIC[2]
* mesa: add default function for ctx->Driver.CheckQuery() hookBrian Paul2009-06-113-1/+19
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-20 18:39:16 +0000