Age | Commit message (Collapse) | Author | |
---|---|---|---|
2008-02-27 | r300: add artificial output to match fragment program input | Markus Amsler | |
2008-02-25 | [r300] Add more struct names for r300_hw_state | Christoph Brill | |
2008-02-25 | [r300] rename all unkown structs r300_hw_state to readable names | Christoph Brill | |
2007-11-05 | Renamed the R300_VAP_UNKNOWN_221C to R300_VAP_CLIP_CNTL. | Oliver McFadden | |
2007-11-05 | r300: initial user clipping for TCL paths | Dave Airlie | |
I've no idea if this code might break something or how it should interact with vertex shaders, it makes the clip demo work for me | |||
2007-07-18 | r300: Cleaned up vertprog construction. | Oliver McFadden | |
Construct the vertprog instruction in the 4 DWORD parts... DWORD 0: Opcode and Output. DWORD 1: First Argument. DWORD 2: Second Argument. DWORD 3: Third Argument. Allow the opcode translation functions to generate more than one instruction; useful for when an instruction must be emulated. FLR, XPD, etc. | |||
2007-07-16 | r300: Use the R300_PVS_UPLOAD_* defines. | Oliver McFadden | |
2007-07-16 | r300: Replaced the ugly VERTEX_SHADER_INSTRUCTION typedef. | Oliver McFadden | |
2007-07-01 | Merge branch 'r300-swtcl' | Dave Airlie | |
2007-06-24 | r300: Initial work on merging the real and generated vertex program functions. | Oliver McFadden | |
2007-06-24 | r300: Vertex program position end bits are known. | Oliver McFadden | |
Possibly performance may improve by setting it to the last instruction that writes result.position, rather than the last instruction in the vertex program. | |||
2007-06-24 | r300: Removed unused vap_param structure. | Oliver McFadden | |
2007-06-14 | Initial r300 modes for swtcl it compiles!! | Dave Airlie | |
2007-05-30 | r300: Document registers 0x2220 to 0x2230. | Oliver McFadden | |
These registers are per-pixel and per-vertex X and Y clipping planes. | |||
2007-05-30 | r300: Removed the (completely broken since new VBO branch) OPTIMIZE_ELTS path. | Oliver McFadden | |
The VTXFMT code was broken by the new VBO branch and the OPTIMIZE_ELTS path relied on the VTXFMT code... I'm not even sure if the OPTIMIZE_ELTS path ever worked; the testing that I did after minimizing the code duplication would have taken the same path as the non-OPTIMIZE_ELTS code. | |||
2007-05-26 | r300: Removed duplicate AOS format defines; already defined in r300_reg.h. | Oliver McFadden | |
2007-05-26 | r300: Removed unused aos_reg variable. | Oliver McFadden | |
2007-05-25 | r300: Cleaned up t_vir0 and t_vir1 slightly. | Oliver McFadden | |
2007-05-22 | r300: Implement SetTexOffset hook. | Michel Dänzer | |
2007-05-20 | r300: Just use "inline" rather than "__inline__". | Oliver McFadden | |
2007-05-17 | r300: Removed the radeon_vertex_buffer structure. | Tommy Schultz Lassen | |
2007-05-13 | r300: Enable the non-user-buffers code to compile. | Oliver McFadden | |
2007-05-13 | r300: Removed the unused r300_aos_rec (replaced by r300_dma_region) structure. | Oliver McFadden | |
2007-05-11 | r300: Removed unused FORCE_32BITS_ELTS define. | Oliver McFadden | |
2007-05-11 | r300: Removed the unused CPT macro. | Oliver McFadden | |
2007-05-11 | r300: Moved r300PackFloat24 near r300PackFloat32. | Oliver McFadden | |
2007-05-09 | r300: Added some more Doxygen documentation and made some functions static. | Oliver McFadden | |
2007-05-09 | r300: Removed the "texmicrotile" variable; the tiling code is disabled via a | Oliver McFadden | |
compiler conditional anyway; probably broken? | |||
2007-05-09 | r300: Cleaned up radeon_context.h slightly; mostly Indent. | Oliver McFadden | |
2007-05-09 | r300: Renamed the R300 memory manager from "radeon" to "r300"; it's R300 | Oliver McFadden | |
specific. | |||
2007-05-09 | r300: Removed the dangerous R300_SPAN_DISABLE_LOCKING flag. | Oliver McFadden | |
Enabling R300_SPAN_DISABLE_LOCKING would probably cause more lockups; I think there are a couple of other little bugs in this code, too. It's best to remove it. | |||
2007-05-09 | r300: Added some Doxygen comments. | Christoph Bill | |
2007-05-09 | r300: Removed the deprecated VTXFMT code. | Oliver McFadden | |
This was okayed by Jerome Glisse and Keith Whitwell on the dri-devel IRC channel and list, respectively. | |||
2007-05-09 | r300: Fixed some more function names. | Oliver McFadden | |
Note there might be some calls to the old function names in conditionally disabled code, but I think I've got them all. | |||
2007-05-09 | r300: Changed r300_run_vb_render calls to r300RunRender in some conditionally | Oliver McFadden | |
disabled code. | |||
2007-05-09 | r300: Indented r300_context.[ch]. | Oliver McFadden | |
2007-05-09 | r300: Removed the ugly CARD32 type. | Oliver McFadden | |
2007-05-09 | r300: Renamed vertex_shader.h to r300_vertprog.h | Oliver McFadden | |
2007-05-08 | r300: Renamed the VBO functions to the R300 name format. | Oliver McFadden | |
2007-05-06 | r300: fix broken vbos | Aapo Tahkola | |
2007-05-05 | don't use hw to perform vertex transform etc. when using swtcl. This for ↵ | Aapo Tahkola | |
compatibility with vertex programs and the fact that swtcl very rarely gets hit with tcl capable hw. | |||
2007-03-24 | r300: Fix texture coordinate calculation for rectangle textures | Nicolai Haehnle | |
R300 hardware takes texcoords in the range 0..1 even for rectangle textures. Previously, the necessary texcoord conversion was applied to the texture coordinate during vertex processing in a render stage. This is obviously wrong when fragment programs are used, which can calculate arbitrary coordinates for TEX instructions. Therefore, we now inject an appropriate MUL instruction before a TEX that reference a rectangle texture. | |||
2007-03-24 | r300: No assertion when accessing incomplete texture images. | Nicolai Haehnle | |
There used to be an assertion when a fragment program accesses an incomplete texture image. Work around this assertion. Note: I am unsure whether this workaround produces the desired result (0,0,0,1) on all hardware. | |||
2007-03-21 | r300: Remove the program-global const_sin index | Nicolai Haehnle | |
The index is no longer necessary to share constants between multiple SIN/COS/SCS instructions inside a single fragment program, and storing a tiny implementation detail like this in the fragment_program structure itself was just nasty. | |||
2007-03-20 | r300: Whitespace cleanup (remove trailing spaces) | Nicolai Haehnle | |
2007-03-19 | r300: Cleanup fragment program constant allocation, share constants | Nicolai Haehnle | |
The constant/parameter allocation was significantly simplified, removing one unnecessary copy operation of parameters. The dirty state tracking is unchanged and far from optimal, since all state is always re-fetched. Constants and parameters are now emitted only once, which significantly reduces the resource pressure on larger programs. | |||
2007-03-19 | r300: Fix fragment program reordering | Nicolai Haehnle | |
Do not move an instruction that writes to a temp forward past an instruction that reads the same temporary. | |||
2007-03-19 | r300: Fix fragment program instruction pairing and register allocation | Nicolai Haehnle | |
There were a number of bugs related to the pairing of vector and scalar operations where swizzles ended up using the wrong source register, or an instruction was moved forward and ended up overwriting an aliased register. The new algorithm for register allocation is quite conservative and may run out of registers before necessary. On the plus side, It Just Works. Pairing is done whenever possible, and in more cases than before, so in practice this change should be a net win. | |||
2007-03-11 | Guess another unknown register in R300 command buffer initialization. ↵ | Aapo Tahkola | |
(Oliver McFadden) | |||
2007-03-11 | Renamed some of the unkXXX variables in the command buffer init | Oliver McFadden | |
ialization code. Note that there are still plenty of actual unknown variables left that should probably be deciphered. There are a number of things incomplete in the driver; the different polygon offset modes (line, point, etc), the other texture filter, texture chroma key, etc. These should probably be fixed in the future, or at least added to the TODO list. |