components/x11/mesa: further fixes and enablement of dri (i915) and gallium (swrast, crocus, iris) drivers #20576
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Temporarily disable until both dri and gallium drivers are confirmed working. Afterwards we can begin further enablement of drivers.
note: swrast_dri.so (traditional swrast dri driver) no longer exists as of Mesa v21. The compatibility symlink currently results in a broken setup due to gallium not yet working. We remove it for now. Mesa 24 introduces 'libdril' a compatibility stub for the legacy DRI loader interface, see https://gitlab.freedesktop/mesa/mesa/-/merge_requests/28378 We can add libdril when we update to Mesa 24. note2: xorg-server will complain about missing swrast_dri.so - there is nothing we can do about that right now. xorg vesa driver will still work.
Revert to i915 dri driver. We can enable i915g gallium driver in future, or use the crocus driver. For now we retain i915 as a legacy dri driver. note: currently broken. Xorg log shows EE for no devices found. I read this to be an error with libdrm as a result of our update in 2024.
note: llvm16 *should* work but is currently broken. This worked until Mesa 21.3.9, thus I am using llvm13 temporarily. see: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8613 note 2: gallium is currently broken but almost working. Upon trying to load kms_swrast_dri there will be an error. Running ::mdb stack on the core will point to a GLESv2 error.
neither of these will work until gallium is working. Enable for now as an example of gallium drivers compatible with existing gfx-drm gate.
|
I have converted this to a draft for the time being. We still need to do a COMPONENT_REVISION bump too. I will have limited time in the next couple of weeks. I will appreciate help here. I will also be at FOSDEM and would be happy to hack on this with anyone in attendance. |
|
Will re-test this following merging of https://github.com/OpenIndiana/gfx-drm/pulls Following that we should have working:
|
|
I maerged the PR's in https://github.com/OpenIndiana/gfx-drm/pulls, You can re-test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per title.
These fixes in addition to the previous fixes I have contributed will result in an almost error free Xorg log. When starting xorg-server there is an error for no devices found. When poking further it is around device initialisation. I read this to be an error in libdrm, resulting from the update in 2024.
When trying to load a gallium driver there is an error. When poked further it leads to libGLESv2.
Outstanding TODO:
With this PR, someone should be able to tweak libdrm and get a working Intel dri setup, just like we had before. Once the initial TODOs are complete i.e. Glamor enablement in xorg-server, we are not far away from a Mesa with working gallium drivers.