summaryrefslogtreecommitdiff
path: root/src/gallium/drivers/i965/brw_batchbuffer.c
AgeCommit message (Collapse)Author
2011-01-09i965g: update to similiar gen stuff as i965Dave Airlie
2010-08-21i965g: Fix printf format warning on 32-bit platforms.Vinson Lee
Fixes the following GCC warning on 32-bit platforms. warning: format '%li' expects type 'long int', but argument 4 has type 'int'
2010-05-17i965g: Fix printf format specifier.José Fonseca
2010-01-20gallium/i965: Make brw_batchbuffer prototypes match in source & headerAlan Coopersmith
Signed-off-by: Alan Coopersmith <alan.coopersmith@sun.com> Signed-off-by: Brian Paul <brianp@vmware.com>
2009-11-30brw: add dumping to gem winsysKeith Whitwell
2009-11-05i965g: propogate map-buffer-range semantics down to winsysKeith Whitwell
2009-11-05i965g: make the winsys responsible for all buffer->offset handlingKeith Whitwell
The winsys now inserts the presumed offset into referring buffers from inside of bo_emit_reloc(). Remove the many locally coded places where this was happening in the driver and eliminate the worry of getting it wrong. No longer need to expose offset values to the driver at all, so no need to worry about what to do in the driver when they change. Just use zero values wherever we had offsets previously -- the relocations will fix it all up for us.
2009-11-05brw: push more dumping into the winsysKeith Whitwell
2009-11-05i965g: add lots of error checks and early returnsKeith Whitwell
Any allocation that may fail should be checked, and propogate the error upwards. At the highest level we will flush batch and retry. This is an alternate strategy to what the original DRI driver did of attempting to flush batch from the lowest levels (eg inside BEGIN_BATCH). The trouble with that strategy was that flushes could occur at unexpected times, and additionally there was a need for a wierd notification mechanism to propogate the 'lost context' state back up to higher levels. Propogating the errors directly gives us a lot of flexibility how to deal with these states, at the expense of a lot more checking in the code. Will add some sanity checks later to make sure that out-of-memory conditions are properly escalated and not lost halfway up the stack.
2009-11-05i965g: add data type tags to aid dumping/decodingKeith Whitwell
2009-11-04i965g: consolidate some includesKeith Whitwell
2009-11-04i965g: pull in a copy of intel_decode.c for nowKeith Whitwell
With the stubbed out, non-hardware xlib winsys, trivial/clear runs and prints a plausible command stream
2009-11-04i965g: fix up batchbuffer confusionKeith Whitwell
2009-11-04i965g: convert read/write domain pairs into single usage valueKeith Whitwell
Easier to understand what's going on in the driver sources, convert stereotype usage values back to GEM read/write domain flags in the winsys.
2009-11-01i965g: driver and winsys compileKeith Whitwell
A milestone of sorts. Still a long way from something working -- the old one compiled too, at least some of the time...
2009-11-01i965g: the whole drivers/i965 directory is compilingKeith Whitwell
That was a lot more work than I expected. Still the winsys to go, then the small matter of making it work and re-enabling the missing functionality.
2009-11-01i965g: more files compilingKeith Whitwell
2009-10-26i965g: still working on compilationKeith Whitwell
2009-10-25i965g: more work on compiling, particularly the brw_draw filesKeith Whitwell