Alyssa Rosenzweig
ece3896d5b
Rebasing around this patch has been a significant burden for development. Staging patches to asahi/mesa helps somewhat but 1. it's still really frustrating to have this much divergence with upstream, and 2. ideally we wouldn't have to do that. The kernel upstreaming is stalled for various reasons. This patch adds compile-only code to speak the unstable Linux UAPI for the SOLE purpose of reducing my rebase pain... NOT to actually work. It is NOT for users OR distro maintainers. asahi will refuse to probe on upstream Mesa to protect against regressions. The uapi is NOT STABLE and upstream Mesa CANNOT be used with it. Attempting to bypass this WILL give you a broken system. This patch employs several layers of deterrents against system-breaking enablement. With a lot of warning text at the relevant sites. Hopefully that is good enough to prevent people from breaking systems. And if people brazenly ignore all of the above ... they get to pick up the pieces. You have been warned. --- There is significant prior art for Mesa including downstream kernel uapi supports in-tree: * powervr (downstream android driver) * turnip (downstream kgsl android driver) * asahi ... ironically (prop macOS kernel driver) * maybe vc4? Linux is only special because of distros shipping tagged Mesa releases. The several layers of guards here guarantee that no tagged Mesa release would possibly probe even on an asahi downstream kernel. A distro would need a significant scary patch to make it probe. If/when it breaks, that's on them and they pick up the pieces. I make a stability guarantee ONLY for Fedora Asahi Remix -- where we push packages for both a downstream kernel and Mesa in tandem, while we patiently wait for upstreaming -- and that is *it*. It will be a nice future when this all works upstream, but unfortunately we're not there yet. Acked by Dave [1] and Sima [2] [1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29620#note_2444189 [2] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29620#note_2445155 Signed-off-by: Alyssa Rosenzweig <alyssa@rosenzweig.io> Co-developed-by: Asahi Lina <lina@asahilina.net> Signed-off-by: Asahi Lina <lina@asahilina.net> Co-developed-by: Sergio Lopez <slp@sinrega.org> Signed-off-by: Sergio Lopez <slp@sinrega.org> Co-developed-by: i509VCB <git@i509.me> Signed-off-by: i509VCB <git@i509.me> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29620>
`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 $ 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://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.