profiles/graphic_drivers: Make a determination of PRIME profile usage… #126
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
vnepogodin
reviewed
Jul 31, 2024
… based on the device name
ventureoo
force-pushed
the
fix-nvidia-prime-profile-again
branch
from
9519ca8 to
50bc6aa
Compare
vnepogodin
approved these changes
Aug 2, 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.
… based on the device name
All (hopefully) NVIDIA mobile card device names contain the suffix
M, which is the always last character before the expanded device nam, so that way we can determine whether or not there is a dGPU without looking at the class ID. Shouldn't cause the regressions that cf2e74a had.