Lines Matching +full:intel +full:- +full:common +full:- +full:rules

11 ----------------
17 .. code-block:: c
37 typically better for human-written code which needs to query for specific
43 parses the vk.xml from the `Vulkan-Docs repo
44 <https://github.com/KhronosGroup/Vulkan-docs/>`__, enumerates the
58 ------------------------------
62 physical device, and device-level functionality.  The device entrypoint
65 .. code-block:: c
93 .. code-block:: c
122 .. code-block:: c
141 ---------------------------------
143 Entrypoint tables can be easily auto-generated for your driver.  Simply put
146 .. code-block::
153         prog_python, '@INPUT0@', '--xml', '@INPUT1@', '--proto', '--weak',
154         '--out-h', '@OUTPUT0@', '--out-c', '@OUTPUT1@', '--prefix', 'drv',
155         '--beta', with_vulkan_beta.to_string(),
161 Vulkan entrypoint, prefixed with what you passed to ``--prefix`` above.
162 For instance, if you set ``--prefix drv`` and the entrypoint name is
164 ``drv_CreateDevice()``.  The ``--prefix`` flag can be specified multiple
173 rules around const struct declarations, it's not practical to generate a
179 .. code-block:: c
187     result = vk_instance_init(&instance->vk, &instance_extensions,
196 instance entrypoints from the Intel Vulkan driver and then adds in the WSI
201 Common Vulkan entrypoints
202 -------------------------
205 ``vk_common`` prefix used to provide common implementations of various
211 most common case is whenever there are ``vkFoo()`` and ``vkFoo2()``
217 .. code-block:: c
234       return device->dispatch_table.BindBufferMemory2(_device, 1, &bind);
246 -----------------
249 Vulkan 1.2 rules around exactly when they have to return ``NULL``.  When a
256  2. Optionally, the index is passed to an auto-generated function that
259     rules for when an entrypoint should be exposed are per-entrypoint.  For
281 ------------------------------------------
289 .. code-block:: c