diff options
| author | Nicolai Hähnle <[email protected]> | 2016-10-07 09:42:55 +0200 |
|---|---|---|
| committer | Nicolai Hähnle <[email protected]> | 2016-10-12 18:50:10 +0200 |
| commit | 700a571f8963cff4bff230e8e9b25da0bdce4f54 (patch) | |
| tree | 7f95890b076177981193d4a193b0aaf0e33c1b3f /src/gallium/docs/source | |
| parent | b33cb709fd06006d4c51824f850a4bb6d8d11f98 (diff) | |
gallium: add PIPE_CAP_TGSI_ARRAY_COMPONENTS
This is a screen cap because drivers are expected to support it either
for all shader types or for none of them.
Reviewed-by: Edward O'Callaghan <[email protected]>
Reviewed-by: Dave Airlie <[email protected]>
Diffstat (limited to 'src/gallium/docs/source')
| -rw-r--r-- | src/gallium/docs/source/screen.rst | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst index cfc0a1b727a..d79e75e2146 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -353,6 +353,14 @@ The integer capabilities: 32-bit. If set to off, that means that a B5G6R5 + Z24 or RGBA8 + Z16 combination will require a driver fallback, and should not be advertised in the GLX/EGL config list. +* ``PIPE_CAP_TGSI_ARRAY_COMPONENTS``: If true, the driver interprets the + UsageMask of input and output declarations and allows declaring arrays + in overlapping ranges. The components must be a contiguous range, e.g. a + UsageMask of xy or yzw is allowed, but xz or yw isn't. Declarations with + overlapping locations must have matching semantic names and indices, and + equal interpolation qualifiers. + Components may overlap, notably when the gaps in an array of dvec3 are + filled in. .. _pipe_capf: |