mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-02-06 08:10:29 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
c0aa3c8323
It's a little unclear from the GLX_ARB_create_context spec whether the list of supported extensions means what the client supports at all, or what it knows an indirect GLX encoding for. You'd think it could only really matter for indirect, since the only way the server would know about GL commands (as opposed to GLX commands) is if the context was indirect. And indeed for Xorg's GLX it doesn't matter, because it doesn't check this, assuming that anything a direct client says works works, and clamping the GL version based on the protocol it has code for. But if you're NVIDIA, apparently, you check this even for direct contexts. And since drisw creates a nominally "direct" context, this means llvmpipe and friends get clamped to 3.0 for desktop GL (since that's as far as the protocol is defined) and can't do GLES at all. So, whatever, just go ahead and claim to support everything. The wire representation of the supported versions is strange (see comments in the code) but it matches what NVIDIA does. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7369> |
||
|---|---|---|
| .appveyor | ||
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| bin | ||
| build-support | ||
| docs | ||
| doxygen | ||
| include | ||
| scons | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| Android.common.mk | ||
| Android.mk | ||
| appveyor.yml | ||
| CleanSpec.mk | ||
| common.py | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| REVIEWERS | ||
| SConstruct | ||
| 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 `Freenode's #dri-devel <irc://chat.freenode.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.