hal/linux: Work around Intel+Nvidia presentation conflict #1898
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
cwfitzgerald
approved these changes
Sep 2, 2021
|
published in wgpu-hal-0.10.4 |
kvark
removed
the
PR: needs back-porting
This was referenced Mar 4, 2024
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.
Connections
This periodically shows up and is very annoying: #1877 (comment) and potentially #1672
Also fixed upstream around 4 month ago - https://gitlab.freedesktop.org/mesa/mesa/-/issues/4688
I think there is still value in handling that internally, at least until we can detect that the Intel driver is fixed.
Description
Vulkan on Linux: if we detect Intel iGPU + NVidia dGPU, we disable presentation on Intel.
The PR also fixes the
compatible_surfaceargument in the util and framework.Testing
Manually tested on my laptop!