| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
In build/xxx/src/gallium/targets/libgl-xlib/SConscript
|
|
|
|
|
| |
Context may become NULL and we still have to be able to flush
pending fences.
|
|
|
|
|
|
|
| |
It's not supposed to do conversion, but st sometimes asks us to.
Sometimes conversion is even wrong (e.g. between UNORM and SRGB).
This should now include all formats the 2D engine supports.
|
| |
|
|
|
|
|
|
| |
Component alpha is temporarily disabled since it seems a bit buggy.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
|
|
|
| |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
|
| |
|
|
|
|
|
|
| |
Part of the fix for https://bugs.freedesktop.org/show_bug.cgi?id=38729
NOTE: This is a candidate for the 7.11 branch
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
| |
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
|
|
| |
r600_is_vertex_format_supported().
Signed-off-by: Henri Verbeet <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
It should be
max_index = start + count - 1
instead of
max_index = count - 1
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.ac
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Typically this was done by having a surface creation function fail if
the format was not supported.
However, in some situations when changing hardware surface formats,
it's desirable to do this check before attempting costly readback operations.
Also updated the surface_redefine interface.
Bump minor.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| |
| |
| | |
The code forgot to increment a pointer.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| |
| |
| |
| | |
Throttle pretty hard in order to prioritize user-space interactivity over
3D application speed. May revisit this later.
Signed-off-by: Thomas <[email protected]>
|
| |
| |
| |
| |
| |
| | |
See the file src/gallium/state_trackers/xa/README for more info.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a regression introduced with commit
"st-api: Rework how drawables are invalidated v3"
where the glx state tracker manager would invalidate a drawable each time it
checks the drawable dimensions, even during a validate call, which
resulted in an endless loop, since the state tracker would immediately
detect the new invalidation and rerun the validate...
This change marks the drawable invalid only if the drawable dimensions actually
changed during the validate, which will result in at most a single
unnecessary validate by the context running a validate during which the
dimensions changed.
To avoid unnecessary validates altogether, we need to implement yet another
st-api change: Returning the current time stamp from the validate function,
as suggested by Chia-I Wu. The glx state tracker manager could then return
the stamp resulting from the last drawable dimension check.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
NOTE: This is a candidate for the 7.11 branch.
|
| |
| |
| |
| |
| |
| | |
Instead of always using the first element's size.
This fixes flashing floor on CINEBENCH R10.
|
| |
| |
| |
| |
| | |
pipe_buffer_map_range makes stricter assertions, and would have saved us
grief detecting a bug in svga user buffer uploads.
|
| |
| |
| |
| | |
Signed-off-by: José Fonseca <[email protected]>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If a user-buffer was referenced twice by a draw command, the affected ranges
were uploaded separately, with only the last one being referenced by the
hardware. Make sure we upload only a single range.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We currently always treat contents of user-buffers as volatile so
we don't need to take any particular action when the state tracker
announces that the contents has changed.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
| |
| |
| |
| | |
See preceeding commit for more info.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Viewperf uses some unusual vertex arrays where the stride is less
than the element size. In this case, the stride was 4 while the
element size was 12. The difference of 8 bytes causes us to miss
uploading the tail bit of the array data.
Typically the stride is >= the element size so there was no problem
with other apps.
|
| | |
|