mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-02-07 01:30:26 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
Follow up of "vulkan/wsi/wayland: add default dma-buf feedback support". The surface feedback is dynamic, differently from the default feedback. When we receive per-surface feedback, that means that we could be using a better DRM format/modifier pair for the chain's buffers. So the next time that the client calls vkAcquireNextImageKHR(), we return VK_SUBOPTIMAL_KHR instead of VK_SUCCESS. Some clients will re-create the swapchain when receiving SUBOPTIMAL, and for those we'll re-create the chain. An optimal DRM format/modifier pair from the per-surface feedback will be used to create the images of this swapchain. Note that for now we won't be able to change the DRM format, only the modifier. That's good enough for many cases in which direct scanout would not be possible because of the modifier. In order to be able to switch the format, we'll need a mechanism to negotiate preferred formats with clients. Currently we can only expose a set of supported formats all with the same preference. Reviewed-by: Simon Ser <contact@emersion.fr> Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12226> |
||
|---|---|---|
| .github/workflows | ||
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .graphqlrc.yml | ||
| .mailmap | ||
| CODEOWNERS | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| VERSION | ||
`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.