Christian Gmeiner
0c6c1fa484
Add support for hardware-accelerated transform feedback using the TFB command register to control capture state. Maintains the hardware state through an enum distinguishing between idle (no hardware state established), active (hardware currently capturing), and paused (hardware stopped). Hardware commands are emitted based on state transitions: - ENABLE when moving from idle to active - RESUME when transitioning from paused to active - DISABLE when stopping capture Transform feedback buffer setup is using the existing dirty state mechanism through ETNA_DIRTY_STREAMOUT_BUFS, while command emission uses the new ETNA_DIRTY_STREAMOUT_CMD flag. Buffer descriptors are computed by mapping vertex shader transform feedback outputs to fragment shader input registers, as required by the hardware. A 64-byte context buffer is allocated per context to maintain hardware state isolation between applications using transform feedback simultaneously. The hardware state persists across pause and resume cycles within a command stream but resets during flushes since transform feedback state does not survive command buffer boundaries. The implementation enables the full transform feedback capability with support for 4 buffers and up to 64 separate or interleaved components, replacing the previous debug-only stub implementation. Signed-off-by: Christian Gmeiner <cgmeiner@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37320>
`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://docs.mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://docs.mesa3d.org/meson.html>`_): .. code-block:: sh $ meson setup build $ ninja -C build/ $ sudo ninja -C build/ 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://docs.mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://docs.mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.