WIP linux-dmabuf vesion 6 (target device) #1273
Draft
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
ids1024
force-pushed
the
dmabuf-target-device
branch
from
39591cd
to
5c24276
Compare
|
Rebased and updated to use |
Draft
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.
Basic implementation of https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/268.
Can be tested along with https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26912.
Will require compositor to do something with the
target_devicefor this to be useful. So far this and the Mesa PR don't do anything too interesting, but should be a good start for trying to improve how multiple GPUs are handled.