| Age | Commit message (Collapse) | Author |
|---|
|
|
|
width/height/depth arrays
|
|
|
|
|
|
Always test for PIPE_TRANSFER_READ/WRITE using the bit-wise and operator, and
add a pipe_transfer_buffer_flags() helper for getting the buffer usage flags
corresponding to them.
|
|
|
|
|
|
|
|
So that messages are in sync with stderr.
|
|
|
|
before/after transfers.
|
|
|
|
And there is no way to override a builtin module... sigh
|
|
|
|
|
|
|
|
Try to keep backwards compatability with old traces as much as possible.
|
|
Only allows clearing currently bound buffers, but colour and depth/stencil in
a single call.
|
|
Surfaces are now by definition GPU views. So CPU access flags don't make
any sense when creating a surface.
For now we are forcing surfaces to be GPU read/write, but that will go away
soon.
|
|
|
|
To make it easy associate images with the calls.
|
|
TODO: Modify the trace driver to generate these on the XML file itself.
|
|
|
|
|
|
|
|
|
|
|
|
C code instead of interpreted python code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
everything into memory).
|
|
|
|
|
|
|
|
They are often left in memory mapped files, and are not part of the XML
accept chars anyway.
|
|
|
|
Now capable of replaying trivial/quad-tex-2d
|
|
To simplify looking up these in the trace.
|
|
|
|
At the moment it is capable of replaying trivial/tri kind of apps.
See README for status.
|
