Update README.md #1074
Merged
Update README.md #1074
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
The idea of this commit is to emphasize the differences between the bazzite and bazzite-nvidia rebase requests. Emphasizing that the former will give you access to NVK but that it is prone to bugs and not to submit issues with Ublue/Bazzite but rather Mesa who is the maintainers of the driver at the time of writing. Hyperlink was added to clearly direct users of where to submit said bugs if need be The latter emphasizing that the -nvidia requests come with NVIDIAs Proprietary drivers, not NVK with the rebase examples
|
@KyleGospo Could i have you look at this and see if everything is good? |
|
Looks good, but let me merge next Mesa update. NVK still isn't quite ready. Thanks for the PR! |
KyleGospo
added a commit
that referenced
this pull request
May 23, 2024
* chore: Update steamdeck-dsp package * Update README.md The idea of this commit is to emphasize the differences between the bazzite and bazzite-nvidia rebase requests. Emphasizing that the former will give you access to NVK but that it is prone to bugs and not to submit issues with Ublue/Bazzite but rather Mesa who is the maintainers of the driver at the time of writing. Hyperlink was added to clearly direct users of where to submit said bugs if need be The latter emphasizing that the -nvidia requests come with NVIDIAs Proprietary drivers, not NVK with the rebase examples --------- Co-authored-by: Kyle Gospodnetich <me@kylegospodneti.ch>
aaron-trout
pushed a commit
to aaron-trout/bazzite
that referenced
this pull request
May 23, 2024
* chore: Update steamdeck-dsp package * Update README.md The idea of this commit is to emphasize the differences between the bazzite and bazzite-nvidia rebase requests. Emphasizing that the former will give you access to NVK but that it is prone to bugs and not to submit issues with Ublue/Bazzite but rather Mesa who is the maintainers of the driver at the time of writing. Hyperlink was added to clearly direct users of where to submit said bugs if need be The latter emphasizing that the -nvidia requests come with NVIDIAs Proprietary drivers, not NVK with the rebase examples --------- Co-authored-by: Kyle Gospodnetich <me@kylegospodneti.ch>
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.
The idea of this commit is to emphasize the differences between the bazzite and bazzite-nvidia rebase requests. Emphasizing that the former will give you access to NVK but that it is prone to bugs and not to submit issues with Ublue/Bazzite but rather Mesa who is the maintainers of the driver at the time of writing. Hyperlink was added to clearly direct users of where to submit said bugs if need be
The latter emphasizing that the -nvidia requests come with NVIDIAs Proprietary drivers, not NVK with the rebase examples