Update GPU plugin README driver section #2105
Merged
Conversation
This file contains hidden or 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
tkatila
reviewed
Aug 18, 2025
eero-t
force-pushed
the
gpu-readme
branch
3 times, most recently
from
f333a04 to
e9831da
Compare
mythi
reviewed
Aug 20, 2025
Signed-off-by: Eero Tamminen <[email protected]>
Typo fixes, add HW support table link, and update k8s resource descriptions Signed-off-by: Eero Tamminen <[email protected]>
Better phrasing + typo fix.
tkatila
approved these changes
Aug 20, 2025
|
I just noticed that the there's also another doc about drivers: https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/cmd/gpu_plugin/driver-firmware.md That would also need an update, as currently it does not even mention I was also wondering whether it would make sense to move the "KMD and UMD" section in README to there, and just link it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I noticed driver information being rather out of date. Checked the drivers a bit and updated README accordingly: