Kenneth Graunke
c46d3acf0e
This raises our vertex input bindings limit from 28 to 31, and our vertex input attribute limit from 28 to 29. We could theoretically go higher, but it will take additional work. The 3DSTATE_VERTEX_BUFFERS and 3DSTATE_VERTEX_ELEMENTS limits are 33 vertex buffers, and 34 vertex elements. But we need up to two vertex elements for system values (FirstVertex, BaseVertex, BaseInstance, DrawID), and we currently use two vertex bindings for those. There is another hidden limit: our compiler backend only supports the push model for VS inputs currently. 3DSTATE_VS only allows URB Read Lengths between [0, 15], which is measured in pairs of inputs, which means we can theoretically push no more than 32 vertex elements. This is no artifical limit either, as a vec4 element takes up 4 registers in the payload, and 32 * 4 = 128, the entire size of our register file. Plus, the VS Thread payload needs at least g0 and g1 for other things, so we can really only push 31. We can theoretically support one additional binding, by combining our two SGV bindings into a single upload. In order to support additional vertex elements, we would need to add support to the backend compiler for the pull model for VS inputs. References: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5917 Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14991>
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.