aboutsummaryrefslogtreecommitdiffstats
path: root/src/mesa/drivers/dri/r200/r200_vertprog.c
Commit message (Collapse)AuthorAgeFilesLines
* radeon/r200/r300: initial attempt to convert to common context codeDave Airlie2009-01-141-2/+2
|
* radeon/r200: move more stuff closer together in contextDave Airlie2009-01-141-1/+1
|
* replace __inline and __inline__ with INLINE macroBrian Paul2008-06-211-2/+2
|
* r200: accept PROGRAM_CONSTANT inputs due to mesa changesAndrew Randrianasulu2008-04-171-0/+1
|
* r200: fix XPD vertex program instruction when using temps as inputsRoland Scheidegger2008-04-121-3/+13
| | | | | | | due to the two read ports limit into temp memory may need the MAD_2 instruction for the second instruction of the decomposed XPD. While here, also try to avoid MAD_2 for MAD if all 3 inputs are temps but the temps aren't actually distinct.
* rx00: fix off by one error in tempreg checkHans de Goede2008-01-021-4/+6
|
* Fix-up #includes to remove some -I options.Brian2007-09-111-4/+4
| | | | eg: #include "shader/program.h" and remove -I$(TOP)/src/mesa/program
* Update DRI drivers for new glsl compiler.Brian2007-02-231-4/+6
| | | | | | Mostly: - update #includes - update STATE_* token code
* r200: simplify / unify input map handling for vp and fftnlRoland Scheidegger2007-02-091-4/+13
| | | | | | Use the same input map handling for fftnl and vertex programs. It doesn't enable any new functionality (should make it easy to support per-vertex materials though), but the code is much cleaner.
* fix errorneously adding fog state params to all vertex programs...Roland Scheidegger2007-02-031-1/+1
|
* submit vertex weights to make World of Warcraft maybe happy (bug 8250)Roland Scheidegger2006-12-141-1/+0
| | | | | | | submit the vertex weights to hw, which will enable broken vertex programs errorneously using them to work. Note however that this will only work if glWeight is used, there is no code in mesa at all to deal with weight vertex array (glWeightPointerARB).
* fix mixed conventional / generic vertex arrays which caused a wrong array ↵Roland Scheidegger2006-11-301-0/+4
| | | | order leading to very bogus rendering (for instance WoW intro screen mentioned in #8250).
* call Driver.ProgramStringNotify if a ati_fragment_shader changes and pick up ↵Roland Scheidegger2006-11-291-0/+3
| | | | the change in the r200 driver accordingly.
* fix using VERT_ATTRIB_WEIGHT instead of VERT_BIT_WEIGHT when assigning vp ↵Roland Scheidegger2006-11-051-1/+1
| | | | inputs.
* enable generic arrays for r200 hw vertex programs by assigning unused color ↵Roland Scheidegger2006-11-031-19/+79
| | | | and texture inputs to them. Not widely tested yet. This should eliminate all fallbacks due to vertex programs, except writes to back facing colors, or when exceeding a hw limit (12 temps, 12 attribs etc.).
* remove code for inserting mvp transform into position-invariant vertex progs ↵Roland Scheidegger2006-10-261-96/+7
| | | | and instead use _mesa_insert_mvp_code().
* change some bogus comments regarding the base e exponential function used ↵Roland Scheidegger2006-10-251-4/+4
| | | | for fog in vertex programs.
* fix (per-vertex) fog when using ARB_vp by incorporating fog factor ↵Roland Scheidegger2006-10-241-31/+119
| | | | computation into the vertex program (not yet fixed for swtnl). Simplify (and correct) the VTX_TCL_OUTPUT_VTXFMT handling when using vertex programs, turns out it's solely driven by the needs of the past-vertex stage of the pipeline, this should fix lockups with ill-specified applications using vertex programs (for instance applications enabling fog but not writing to fog coord output will now get (conformant) undefined results instead of lockups).
* fix up access to vertex attrib components which don't really exist but are ↵Roland Scheidegger2006-09-221-1/+39
| | | | defined to some default value by the spec (fogcoord yzw, normal w, secondary color w), by replacing those components with zero/one respectively using swizzling.
* make sure we upload the new vertex program if the program string changes.Roland Scheidegger2006-09-131-0/+2
|
* make really sure R200_VAP_PROG_VTX_SHADER_ENABLE is never set when we're ↵Roland Scheidegger2006-09-071-1/+1
| | | | already in a tcl fallback, otherwise the chip will instantly lock up when vertex progs are enabled the next time not in a tcl fallback (fixes for instance guaranteed lockup running any program which uses vertex progs with tcl_mode=0 and then later with tcl_mode=1).
* make sure vertex programs are only enabled on the hw when they are really ↵Roland Scheidegger2006-09-011-0/+5
| | | | enabled, not just when a program enables vertex progs (could still be not enabled due to some error). Otherwise the hw potentially would try to execute a not valid (not set up at all) vertex program, likely leading to lockups. Hopefully fixes #8060.
* do not abort with not supported vertex prog output configuration, fallback ↵Roland Scheidegger2006-08-311-3/+19
| | | | instead
* Minor r200 vertex program cleanups. Remove disabled leftovers from r300 ↵Roland Scheidegger2006-08-301-61/+23
| | | | vertex program code. Fix authors. Correct slightly wrong check to determine if ran out of temps. Simplify check to determine if ran out of max instructions. Correctly report used native temps. Always kick off program translation when ProgramStringNotify is called (otherwise the reported native resources used queried might be wrong).
* fix typo causing a segfault when a vertex program uses more than 96 parametersRoland Scheidegger2006-08-301-1/+1
|
* Check mesa_vp->Base.NumInstructions == 0 instead of mesa_vp->Base.String toBrian Paul2006-08-281-1/+1
| | | | determine if we actually have a program. See "[r300] TCL fallback with Quake3".
* Check for NULL program string in r200_translate_vertex_program().Brian Paul2006-08-241-2/+18
| | | | | Fixes bug reported by Chris Rankin. Added some new comments.
* Check if mesa_vp->Base.Parameters is null before dereferencing (bug reportBrian Paul2006-08-241-3/+6
| | | | | from Chris Rankin). Also, fix some bad casts.
* Some structure renaming. Prefix vertex/fragment-related structs withBrian Paul2006-07-201-11/+16
| | | | "gl_" to match other structs.
* some minor simplifications (same as in r300 driver) since mesa's internally ↵Roland Scheidegger2006-07-031-23/+17
| | | | used swizzle and writemask flags are identical to the bits used on the hardware, use a macro to error out if these assumptions are no longer true.
* no need to handle ARL in a special way, it's a generic scalar operation. ↵Tilman Sauerbeck2006-06-181-10/+4
| | | | only tested on r300.
* enable arb_vertex_program by default if drm is new enough. Do a fallback ↵Roland Scheidegger2006-06-101-0/+5
| | | | when it's a nv_vp as there could be issues.
* Improve slightly wrong CMP_SRCS test to avoid unencessary instructions. ↵Roland Scheidegger2006-06-081-94/+54
| | | | Clean up the r200 vertex program code a bit.
* implement arb_vertex_program in hw for r200. Code contains still some hacks, ↵Roland Scheidegger2006-06-021-0/+1180
generic attribs cause a fallback, but otherwise it seems to work quite well. Passes all glean vertProg1 tests with the exception of the degnerated LIT case (which is a hw limitation), as well as runs the r200 render path of doom3/quake4 (1.1 patch needed for quake4). The code is heavily borrowed from the r300 driver as vertex programs encoding is almost identical. arb_vertex_program is not yet announced by default and still needs to be enabled via driconf.