mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-06-06 19:18:15 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
e32f7ac381
There's a few things going on here: 1. Vulkan makes the YCbCr model and YCbCr range completely orthogonal. This means that we need to be able to handle an identity transform while still doing range-remapping, so we apply the range mapping and color-transform separately, and let the optimizer clean things up. This is similar to what we did before, but it means it's a bit harder to get completely optimal code out of this. 2. Vulkan defines that the YCbCr inputs come in a bit of an unusual order; Cr, Y, Cb. This means we need to reorder things a bit when applying the YCbCr range and multiplying the YCbCr color-model matrix. This makes the code a little bit confusing to read at times. 3. Because the alpha-channel is passed through this function, we need to expand the matrix to 4x3. This is similar to what we've already been doing, but also a bit unusual. In the future, we might want to keep the alpha-channel out of this code-path, and just work on a vec3 here. I suspect that all of these can be solved by rearranging the code a bit. But I've left that as an excercize for later to make sure we get this right first, with as few modifications as possible. Some people might disagree with this approach, but let's see. Reviewed-by: Eric R. Smith <eric.smith@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40175> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| .marge/hooks | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| licenses | ||
| src | ||
| subprojects | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .clang-format-include | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .graphqlrc.yml | ||
| .mailmap | ||
| .mr-label-maker.yml | ||
| .shellcheckrc | ||
| clippy.toml | ||
| CODEOWNERS | ||
| meson.build | ||
| meson.options | ||
| README.rst | ||
| rustfmt.toml | ||
| 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://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.