WIP: Mesa/drm/dri fixes #19641
WIP: Mesa/drm/dri fixes #19641
Conversation
Add an array DRI_DRIVERS to the Makefile: - This array can be expanded in future with examples as listed - Take caution with the example list: some e.g. i965 are removed beginning in Mesa v22.x - Gallium drivers are the most supported in the newest versions of Mesa
Add an array GALLIUM_DRIVERS to the Makefile: - This array can be expanded in future with examples as listed - Take caution when adding support for e.g. swrast as it will split into softpipe and llvmpipe in future - swrast is currently disabled due to it's dependency on llvm v16 - r600 temporarily disabled
Add an array VULKAN_DRIVERS to the Makefile: - This array can be expanded in future with examples as listed - Take caution when adding support for e.g. swrast as it will split into softpipe and llvmpipe in future - nothing is enabled as there is some pre-requisite work to be done first
This becomes unconditionally enabled upstreamed [1] in Mesa 24.3, or Mesa 25. As highlighted in the referenced merge request: - This existed for historical reasons, now possible to build Mesa with DRI3 always enabled - In reference to the above, e.g. classic drivers removed from Mesa 22.x onwards - This check was often used as a substitute for having drm functionality - Prevents users from footgunning themselves [1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30952
This enable option has existed since at least Mesa 18.
The classic swrast driver was removed upstream (Dec 2020) in commit 435de835cd63
|
Please find package x11/library/glslang version 14.3.0 is now available. |
|
Hi @xmhd good to see someone coming into OpenIndiana packaging. And thanks for the work! Usually what we do while reviewing, is we try to compile this on a set of machines to coax out some hidden things that auto-magic is detecting so we can make this reproducible. I found some things during that process. Apparently, only one type of i915 driver can be enabled at the same time. I get When commenting out either It could be that we also need libunwind https://github.com/libunwind/libunwind which seems to be straight forward or that some option is requiring llvm now we have already started to provide llvm16 again on the system to support this effort here. lastly we will need to split each component into it's own PR so that we can make sure the build system builds them in the right order. We still have to do this manually. We can keep it in this PR for now to make sharing code easier during development phase. Loving the work so far. Let's get this over the finish line. |
|
@Toasterson Thanks for initial review - I realise that I missed submitting a few changes hence why you hit issues. And yeah no worries re: splitting this into multiple PRs etc afterwards, this can just serve as the staging ground for getting this working again. I'll pick it up this weekend and see if I can get it over the finish line. |
| @@ -32,6 +33,16 @@ include $(WS_MAKE_RULES)/common.mk | |||
|
|
|||
| PATCH_LEVEL= 0 | |||
|
|
|||
| # Mesa 21.x requires 2.4.100 - 2.4.109 | |||
| # Mesa 22.x requires 2.4.9 - 2.4.110 | |||
There was a problem hiding this comment.
Shouldn't this read 2.4.109 instead of 2.4.9 ?
There was a problem hiding this comment.
Yes indeed, good catch. I'll fix this tonight.
|
Please find LLVM 16 in packages developer/clang-16 and runtime/clang-16 . I looked at libunwind--it doesn't have enough Solaris/illumos support to be useful. Adding this to the mesa Makefile will ensure libunwind does not get used: |
Obsoletes #19640
As per title. This pull request serves as the beginning of fixing the currently broken state of Mesa / DRM / DRI in OpenIndiana, which has been broken since 7defdf1
The problems which I have identified thus far:
With the above in context, starting from a fresh install of OpenIndiana Hipster and updating to the latest available packages, only Vesa (not related to Mesa for the uninformed) is enabled. In this state neither glxinfo nor glxgears are available.
With the changes in this pull request I haven't quite gotten things working to the state that they were previously i.e. accelerated Intel graphics on a Thinkpad X230, but glxinfo and glxgears are now working. I've spent quite a few hours on this problem over the weekend and I have been discussing it with @Toasterson throughout. I will not have any more time to work on this until next weekend at the earliest. Please contribute and we can get this working again before continuing on to further improving the graphical desktop experience with things such as libva, Vulkan and more in Mesa.
Note: