Age | Commit message (Collapse) | Author |
|
|
|
It's necessary to download buffers from the host always, except if the
buffer is undefined, because:
- just PIPE_BUFFER_USAGE_CPU_WRITE doesn't guarantee all data is written
-- old contents may still pierce through
- PIPE_BUFFER_USAGE_DISCARD refers to a range, not the whole buffer, so
unless we track which parts have been modified and not we still need
to download the data.
|
|
|
|
|
|
|
|
It could erroneously return PIPE_OK in some circumstances.
Make compile_fs code identical.
|
|
|
|
To ensure that a new result that happens to have the same address
of the old one will be detected as a change.
|
|
Even shader ID doesn't change. Otherwise the token change is not
effective.
This reverts regression from commit
cdb445f3a9285e2d8f042a07021ade78b94e0156. Regression could be seen in
Quake3's loading screen -- the upper right corner of the screen would
be black.
|
|
|
|
|
|
Make it easier to insert/remove error branches.
|
|
Thanks for Keith to finding this.
Fixes Jedi Knight 2 menus.
|
|
Since we're reusing buffers we're effectively transforming all
of them into dynamic buffers.
It would be nice to not cache long lived static buffers. But there
is no way to detect the long lived from short lived ones yet. A
good heuristic would be buffer size.
|
|
The texture owns the surface handle. All derivatives need to keep
a reference to texture.
This fixes several assertions failures starting up Jedi Knight 2.
Should cause no change for DRM surface sharing -- reference count still
done as before there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This helps improve the surface cache behaviour in the face of the
large number of single-use render targets generated by EXA and the xorg
state tracker. Without this we can reference hundreds of individual
render targets from a command buffer, which leaves little scope for
sharing or reuse of those targets.
Flushing early means we can start reusing textures much sooner.
This shouldn't have much effect on normal 3d rendering as it's pretty
rare to have a command buffer with >8 different render targets in that
world.
|
|
|
|
|
|
|
|
It doesn't though.
|
|
Over-ambitious packing of values broke my cursor.
|
|
|
|
Rather have the driver compile without the flags then
having to disable them.
|
|
Remove x86 specific hacks. Not that they will ever be used on
none x86 arches, but they are built by default. And the way the
flags where added was a hack.
|
|
|
|
|