summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/dri/radeon/radeon_tcl.c
AgeCommit message (Collapse)Author
2008-05-26Remove CVS keywords.José Fonseca
2006-10-31remove vtxfmt code, switch over to vboKeith Whitwell
2006-09-10remove code to deal with non-normalized texture coordinates for tex rect ↵Roland Scheidegger
targets (swtcl tex coord translation stage, tcl tex matrix adaption) and use the chip's native handling of such coords instead (!!!). Seems noone noticed those bits in the se_coord_fmt reg, even though it works fairly similar to r200 (except it's set per-unit and always active, so only enable it for texture rectangles).
2005-10-29Bug #4901: Correct secondary color emission when lighting is turned off, testedEric Anholt
with seccolor on rv200 and r200. Submitted by: sroland
2005-10-17add GL_EXT_fog_coord support to radeon driver. No vtxfmt code (just uses ↵Roland Scheidegger
fallback) yet. May cause a tcl fallback if fog coord is used together with separate specular lighting. Fog factors are precomputed and then submitted instead of the raw coords (chip limitation, same as on r200).
2005-10-05Remove the tcl fallback for texture rectangle (by manipulating the texture ↵Roland Scheidegger
matrix) (tested with texrect). Enable texgen for r/q coordinates (tested with projtex). Fix projected texcoords when an app uses TexCoord3x and the texture matrix to save on vertex size (fixes ut2k3 shadow projectors in tcl mode). From texgenmix, all cases with all texgen or no texgen work, with the exception of texgen enabled for s/t only, this one works with hw tcl, but not with vtxfmt (suspect issues with vtxfmt), the mixed cases do not work (which is expected, and should be rare in practice), with the exception of the first one which hits a tcl fallback.
2005-07-15remove duplicate "User disable" stringBrian Paul
2005-07-14added a few more fallbackStrings (Andreas Stenglein)Brian Paul
2005-05-16Apply r200 tcl fix to radeon - compiles but untested.Keith Whitwell
2005-04-22First pass at updating these drivers with pipeline_stage struct changes.Keith Whitwell
2005-02-16s/0/NULL/ (Jeff Muizelaar)Brian Paul
2004-12-14uint*t -> u_int*t changesAlan Hourihane
2004-12-02silence warningsAlan Hourihane
2004-11-12brown paper bag, r100 can't do hardware quads.Adam Jackson
2004-11-12make render_quads_verts call EMIT_PRIM with the arguments in the right order,Adam Jackson
and enable hardware quads on r200 and radeon. samples/prim renders quads correctly now.
2004-09-24Clean up some warnings in the R100 driver with -O -Wall.Eric Anholt
2004-08-17Close some races with locking on R100 and R200 which could manifest as renderingEric Anholt
errors on r100 and rendering errors and hangs on r200 (same for R100 without OLD_PACKETS). If a command buffer filled after some state (EmitState or a VBPNTR write) was emitted, the lock was grabbed, the buffer flushed, a new buffer prepared, and the lock dropped. Another client could come in, set its own state as part of rendering, and when the first client flushed the rendering commands depending on the previous state, it got the 2nd client's state. This is fixed by checking for enough space before beginning a set of state emits and rendering, and flushing the buffer first if so. This guarantees that the buffer won't wrap. Also, move the "lost_context = 1" from the end of cmdbuf flushing to UNLOCK_HARDWARE for clarity (at a minimum) that any time the lock is dropped, state may get overwritten. We don't have enough information at the point of the LOCK_HARDWARE to reset our state to the last UNLOCK_HARDWARE point in the case that we did lose our context, but saving the information to rebuild that state may be a useful optimization (ipers data suggests up to 5%).
2004-04-08build fixesAlan Hourihane
2003-11-24Import vtx-0-2-branchKeith Whitwell
2003-08-22patch to import Jon Smirl's work from BitkeeperBrian Paul