summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* r300-gallium: Add half-right COS and SIN.Corbin Simpson2009-05-171-0/+9
| | | | | HW trig does a premultiply by 2pi, where Mesa does another premultiply by pi. This is a problem.
* r300-gallium: Size mismatch.Corbin Simpson2009-05-171-1/+1
|
* r300-gallium, radeon-gallium: Nuke gb_pipes from orbit.Corbin Simpson2009-05-177-49/+2
| | | | | See the previous commit for an explanation. This is just all the support code for GB_TILE_CONFIG.
* r300-gallium: Don't set GB_TILE_CONFIG (in userspace.)Corbin Simpson2009-05-171-4/+1
| | | | | | | | | | | | | 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.
* r300-gallium: Clean up more invariant state.Corbin Simpson2009-05-172-24/+13
| | | | GA_ENHANCE is now the kernel's problem.
* r300-gallium: Update XXX.Corbin Simpson2009-05-172-20/+3
| | | | Lops work fine as long as HW TCL is off. (I think I know why.)
* r300-gallium: Correct default MSPOS.Corbin Simpson2009-05-171-2/+2
| | | | Per agd5f.
* r300-gallium: vs: Fix vert shader init.Corbin Simpson2009-05-171-15/+4
| | | | Makes the last three commits suck much less. :3
* r300-gallium: r500-fs: Enable depth writes, kinda.Corbin Simpson2009-05-172-4/+31
| | | | Should work, but doesn't. Hm.
* r300-gallium: Comment out useless debugging code.Corbin Simpson2009-05-171-12/+12
| | | | Those parts are nearly solid compared to the shaders.
* r300-gallium: vs: Dupe tokens, better debug, count spurious insts.Corbin Simpson2009-05-173-6/+23
|
* r300-gallium: Die on bad texture formats.Corbin Simpson2009-05-161-2/+9
| | | | | Odds are good that we'll die later anyway, so we might as well do it before we start dancing on random memory.
* r300-gallium: Update floating-point params too.Corbin Simpson2009-05-161-6/+9
| | | | Even though we *can* render 10,000-pixel-wide lines, let's not advertise it.
* r300-gallium: Update screen caps.Corbin Simpson2009-05-161-4/+3
| | | | Anisotropic filtering should work, and OQ is broken.
* intel-gallium: Fix trace_drm integration.Corbin Simpson2009-05-161-144/+5
| | | | Compile-tested only, sorry.
* Create common trace_drm code, add to radeon_winsys.Corbin Simpson2009-05-164-0/+175
|
* r300-gallium: Various cleanups leftover from before.Corbin Simpson2009-05-163-3/+8
| | | | BEGIN/END_CS pair, a few asserts, and a slightly more correct VTE setup.
* gallium: remove occlusion_count flag from depth-stencil stateKeith Whitwell2009-05-164-2/+7
| | | | | | | | | 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.
* gallium-intel: Enable trace driverJakob Bornecrantz2009-05-163-0/+147
|
* trace: Export enabled statusJakob Bornecrantz2009-05-164-9/+25
|
* trace: Unwrap buffer in texture_blanketJakob Bornecrantz2009-05-161-1/+3
|
* trace: If either shader is disabled don't drawJakob Bornecrantz2009-05-162-0/+19
|
* trace: Put shaders on a list in the contextJakob Bornecrantz2009-05-166-8/+151
|
* trace: Move state dump functions to tr_dump_state.[c|h]Jakob Bornecrantz2009-05-166-7/+7
|
* intel: Don't complain on falling back from PBO fastpaths.Eric Anholt2009-05-151-3/+3
| | | | | | Instead, stash the debug info under the handy debug flag. Bug #20053
* mesa: Mark FBOs with compressed color attachments as FBO-incomplete.Eric Anholt2009-05-151-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.
* gallium-intel: Build with sconsJakob Bornecrantz2009-05-153-0/+39
|
* st/egl: Use proper MakefileJakob Bornecrantz2009-05-151-23/+13
|
* i915: Fix 945 cube map layout for the small mipmaps along the bottom.Steinar H. Gunderson2009-05-151-2/+14
| | | | Bug #21691.
* i915: Use Stencil.Enabled instead of Stencil._Enabled in DrawBuffers.Eric Anholt2009-05-151-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
* i915: Only use the new 945 cube layout for compressed textures.Eric Anholt2009-05-151-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
* i965: Fix varying payload reg assignment for the non-GLSL-instructions path.Eric Anholt2009-05-141-8/+10
| | | | I don't have a testcase for this, but it seems clearly wrong.
* i965: Fix register allocation of GLSL fp inputs.Eric Anholt2009-05-144-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.
* intel: Use FRONT_AND_BACK for StencilOp as well.Eric Anholt2009-05-141-1/+2
|
* intel: Use GL_FRONT_AND_BACK for stencil clearing.Eric Anholt2009-05-141-1/+2
| | | | | This comes from a radeon-rewrite fallback fix, but may also fix stencil clear failure when the polygon winding mode is flipped.
* r300-gallium: Correct VTE setup for surface_fill, make surface_copy emit right.Corbin Simpson2009-05-141-32/+43
|
* i965: fix 1D texture borders with GL_CLAMP_TO_BORDERRobert Ellison2009-05-141-0/+10
| | | | | | | | | | | | | | 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.
* i965: send all warnings through _mesa_warning()Robert Ellison2009-05-141-1/+1
| | | | | | | | | | | 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.
* r300-gallium: Clean up outdated comments.Corbin Simpson2009-05-132-4/+0
|
* r300-gallium: Space accounting for textures.Corbin Simpson2009-05-131-2/+7
|
* Merge branch 'mesa_7_5_branch'Brian Paul2009-05-131-1/+2
|\
| * intel: added null ptr checkBrian Paul2009-05-131-1/+2
| | | | | | | | Fixes segfault in context tear-down when glClear was never called.
* | docs: GL_APPLE_vertex_array_object for Gallium drivers and Intel DRI driversBrian Paul2009-05-131-0/+1
| |
* | intel: enable GL_APPLE_vertex_array_objectBrian Paul2009-05-131-0/+2
| | | | | | | | No special driver changes are needed for this extension.
* | st/mesa: enable GL_APPLE_vertex_array_object for gallium driversBrian Paul2009-05-132-0/+7
| |
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-05-135-45/+93
|\| | | | | | | | | | | | | | | Conflicts: src/mesa/main/arrayobj.c src/mesa/main/arrayobj.h src/mesa/main/context.c
| * intel: create a private gl_array_object for intel_clear_tris(), fix bug 21638Brian Paul2009-05-133-29/+75
| | | | | | | | | | | | | | | | | | 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().
| * mesa: delete array objects before buffer objects during context tear-downBrian Paul2009-05-131-1/+2
| | | | | | | | The former may point to the later.
| * mesa: clean-up vertex array object VBO unbinding and delete/refcountingBrian Paul2009-05-131-31/+33
| | | | | | | | | | | | 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)
| * mesa: reference counting for gl_array_objectBrian Paul2009-05-134-13/+84
| | | | | | | | | | | | Every kind of object that can be shared by multiple contexts should be refcounted. (cherry picked from commit 1030bf0ded2a88a5e27f7a4d393c11cfde3d3c5a)
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-23 21:44:17 +0000