gallium/docs: fixup formatting of numbered lists

Fixes: 0caf74bbcd ("gallium: add PIPE_CAP_FRAMEBUFFER_MSAA_CONSTRAINTS")
Fixes: 8632626c81 ("gallium: add pipe_resource::nr_storage_samples, and set it same as nr_samples")

Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Acked-by: Eric Engestrom <eric@engestrom.ch>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5691>
This commit is contained in:
Erik Faye-Lund
2020-06-30 11:09:20 +02:00
committed by Marge Bot
parent 7f5061c0b7
commit 686cf8eaad

View File

@@ -446,12 +446,14 @@ The integer capabilities:
* ``PIPE_CAP_FRAMEBUFFER_MSAA_CONSTRAINTS``: This determines limitations * ``PIPE_CAP_FRAMEBUFFER_MSAA_CONSTRAINTS``: This determines limitations
on the number of samples that framebuffer attachments can have. on the number of samples that framebuffer attachments can have.
Possible values: Possible values:
0: color.nr_samples == zs.nr_samples == color.nr_storage_samples
0. color.nr_samples == zs.nr_samples == color.nr_storage_samples
(standard MSAA quality) (standard MSAA quality)
1: color.nr_samples >= zs.nr_samples == color.nr_storage_samples 1. color.nr_samples >= zs.nr_samples == color.nr_storage_samples
(enhanced MSAA quality) (enhanced MSAA quality)
2: color.nr_samples >= zs.nr_samples >= color.nr_storage_samples 2. color.nr_samples >= zs.nr_samples >= color.nr_storage_samples
(full flexibility in tuning MSAA quality and performance) (full flexibility in tuning MSAA quality and performance)
All color attachments must have the same number of samples and the same All color attachments must have the same number of samples and the same
number of storage samples. number of storage samples.
* ``PIPE_CAP_SIGNED_VERTEX_BUFFER_OFFSET``: * ``PIPE_CAP_SIGNED_VERTEX_BUFFER_OFFSET``:
@@ -936,6 +938,7 @@ If there are not enough slots to store all sample colors, some samples will
have an undefined color (called "undefined samples"). have an undefined color (called "undefined samples").
The resolve blit behavior is driver-specific, but can be one of these two: The resolve blit behavior is driver-specific, but can be one of these two:
1. Only defined samples will be averaged. Undefined samples will be ignored. 1. Only defined samples will be averaged. Undefined samples will be ignored.
2. Undefined samples will be approximated by looking at surrounding defined 2. Undefined samples will be approximated by looking at surrounding defined
samples (even in different pixels). samples (even in different pixels).