diff options
| author | Edward O'Callaghan <eocallaghan@alterapraxis.com> | 2016-02-17 20:59:52 +1100 |
|---|---|---|
| committer | Dave Airlie <airlied@redhat.com> | 2016-04-07 11:56:44 +1000 |
| commit | 4bc9130fba2f815cb910536d3d3a253a8c3ed0b9 (patch) | |
| tree | 2d69dad9336b94e18822fbf40ac85334abf726ab /src/gallium/docs | |
| parent | 85f79f0c7567e47ca4c5b204ddf7891fd12e3e85 (diff) | |
| download | external_mesa3d-4bc9130fba2f815cb910536d3d3a253a8c3ed0b9.zip external_mesa3d-4bc9130fba2f815cb910536d3d3a253a8c3ed0b9.tar.gz external_mesa3d-4bc9130fba2f815cb910536d3d3a253a8c3ed0b9.tar.bz2 | |
gallium: Add PIPE_CAP_FRAMEBUFFER_NO_ATTACHMENT
Add PIPE_CAP to determine if the GL extension
'GL_ARB_framebuffer_no_attachments' shall be
supported.
The driver is required to support 'PIPE_FORMAT_NONE'
via its 'is_format_supported()' callback in order
to determine the MSAA modes the hardware supports so
that values requested from the application using
'GL_ARB_framebuffer_no_attachments' may be quantized
to what the hardware expects.
V.2:
Fix doc for a more detailed description of the PIPE_CAP
and the corresponding GL constant.
V.3:
Renamed and repurposed once again.
V.4:
Remove CAP from cap_mapping array.
[airlied: fix damaged whitespace]
Signed-off-by: Edward O'Callaghan <eocallaghan@alterapraxis.com>
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'src/gallium/docs')
| -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 47a19de..824f580 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -323,6 +323,14 @@ The integer capabilities: * ``PIPE_CAP_PCI_BUS``: Return the PCI bus number. * ``PIPE_CAP_PCI_DEVICE``: Return the PCI device number. * ``PIPE_CAP_PCI_FUNCTION``: Return the PCI function number. +* ``PIPE_CAP_FRAMEBUFFER_NO_ATTACHMENT``: + If non-zero, rendering to framebuffers with no surface attachments + is supported. The context->is_format_supported function will be expected + to be implemented with PIPE_FORMAT_NONE yeilding the MSAA modes the hardware + supports. N.B., The maximum number of layers supported for rasterizing a + primitive on a layer is obtained from ``PIPE_CAP_MAX_TEXTURE_ARRAY_LAYERS`` + even though it can be larger than the number of layers supported by either + rendering or textures. .. _pipe_capf: |