| Age | Commit message (Collapse) | Author |
|---|
|
several drivers which chose to ignore edgeflags might require some more work,
while edgeflags never worked there they might now crash.
|
|
|
|
Conflicts:
src/gallium/state_trackers/xorg/xorg_exa.c
|
|
|
|
Conflicts:
src/gallium/drivers/r300/r300_vs.c
|
|
|
|
|
|
Drop the 1.1 version suffix.
|
|
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.
|
|
|
|
|
|
|
|
More common. True fix would be to use whatever the screen supports though.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
