Modernize MetaInfo #3
Open
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
Modernize and adapt this metainfo for best description. Fix some errors and remove AVC because is the same part of h264 coded, add h265 that is supported by Mesa3D Gallium VAAPI State Tracker too
Gallium's VA-API State Tracker just support AMD GPUs running AMD Gallium Drivers
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.
Mesa3D uses Gallium Driver architecture for multi vendors GPUs Driver.
Gallium for default uses State Trackers (Gallium Frontends) For implement API in Gallium API.
For default a VDPAU and VA-API are State Trackers for Gallium.
Nvidia can't support VA-API don't have reason to maintain this in VAAPI metainfo