Alyssa Rosenzweig
3de9c42908
There are three tiers of drivers: * Drivers that support MRT and support mixed colorbuffer formats. All modern hardware fits this as it becomes a spec requirement. * Drivers that do not support MRT. Then this CAP is a no-op, so we might as well set it by default even here (this commit trivially enables the CAP for lima, vc4, etanviv). * Drivers that support MRT but do not support mixed colorbuffer formats! Very little hardware fits this category as it doesn't suffice for MRT in most APIs. Unfortunately we have a few drivers that are in this category, preventing us from bulldozing the CAP altogether. Given that the CAP only exists for a few legacy drivers, default it to being enabled to avoid new drivers falling into the trap of forgetting to enable it. Failing to set this CAP causes failures in dEQP-GLES3.functional.fbo.completeness.* Drivers which still do not set this CAP: nv30, r300 (older than r500), virgl in some cases. r300/r400 is due to a hardware requirement as Emma points out. v2: Advertise the cap on lima like the commit message claims (delete the special case). Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Reviewed-by: Marek Olšák <marek.olsak@amd.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19079>
`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.