diff options
author | Marek Olšák <[email protected]> | 2013-03-14 17:18:43 +0100 |
---|---|---|
committer | Marek Olšák <[email protected]> | 2013-03-23 13:19:16 +0100 |
commit | 3e10ab6b22341c06a9352b1e029b923f4d8405b9 (patch) | |
tree | ac3dd22bf0f641b69562204066df4c2e211ef8a6 /src/gallium/docs | |
parent | 25e3094058977648a6f552d59b728a9ea814b7c2 (diff) |
gallium,st/mesa: don't use blit-based transfers with software rasterizers
The blit-based paths for TexImage, GetTexImage, and ReadPixels aren't very
fast with software rasterizer. Now Gallium drivers have the ability to turn
them off.
Reviewed-by: Brian Paul <[email protected]>
Tested-by: Brian Paul <[email protected]>
Diffstat (limited to 'src/gallium/docs')
-rw-r--r-- | src/gallium/docs/source/screen.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst index 0550a30714a..9b8704904ab 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -145,6 +145,10 @@ The integer capabilities: TEXCOORD semantic. Also, TGSI_SEMANTIC_PCOORD becomes available, which labels a fragment shader input that will always be replaced with sprite coordinates. +* ``PIPE_CAP_PREFER_BLIT_BASED_TEXTURE_TRANSFER``: Whether it is preferable + to use a blit to implement a texture transfer which needs format conversions + and swizzling in state trackers. Generally, all hardware drivers with + dedicated memory should return 1 and all software rasterizers should return 0. .. _pipe_capf: |