feat: dynamically set GPU variable in chromium.conf #93
Conversation
This file contains hidden or 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
|
This PR fixed non-working GPU acceleration for me. Ryzen 5 5625U CPU, Vega 7 iGPU. |
RKNF404
approved these changes
Dec 20, 2024
RoyalOughtness
approved these changes
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
different take on #92 that doesn't require egl-utils and should better handle multi-gpu
If there are heterogeneous GPU vendors, it will fallback to default.
This comment about the vulkan flags being experimental is worth heeding, although if they are experimental then it should at least be marked as such, or revised to work as expected.