← Back to branch summary

~mmach/netext73/mesa-ryzen

« back to all changes in this revision

Viewing changes to docs/vulkan/graphics-state.rst

  • Committer: mmach
  • Date: 2023-11-02 21:31:35 UTC
  • Revision ID: netbit73@gmail.com-20231102213135-18d4tzh7tj0uz752
2023-11-02 22:11:57

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/vulkan/graphics-state.rst
30
30
structure will be populated as if for dynamic rendering, regardless of
31
31
which path is used.  Drivers which use their own render pass structure
32
32
should parse the render pass, if available, and pass a
33
 
:cpp:struct:`vk_subpass_info` into
 
33
:cpp:struct:`vk_render_pass_state` to the `driver_rp` argument of
34
34
:cpp:func:`vk_graphics_pipeline_state_fill()` with the relevant information
35
35
from the specified subpass.  If a render pass is available,
36
36
:cpp:struct:`vk_render_pass_state` will be populated with the
37
 
:cpp:type:`VkRenderPass` handle and subpass index as well as the
38
 
information from the :cpp:struct:`vk_render_pass_state`.  If dynamic
39
 
rendering is used or the driver does not provide a
40
 
:cpp:struct:`vk_subpass_info` structure, :cpp:struct:`vk_render_pass_state`
 
37
the information from the :cpp:struct:`driver_rp`.  If dynamic
 
38
rendering is used or the driver provides a `NULL`
 
39
:cpp:struct:`driver_rp`, the :cpp:struct:`vk_render_pass_state`
41
40
structure will be populated for dynamic rendering, including color, depth,
42
41
and stencil attachment formats.
43
42
 
44
 
.. doxygenstruct:: vk_subpass_info
45
 
   :members:
46
 
 
47
43
The usual flow for creating a full graphics pipeline (not library) looks
48
44
like this:
49
45