Repository navigation
Add dual FirePro D300 test results - #1
Merged
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
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.
Reports D300 validation on a MacPro6,1 with dual FirePro D300 GPUs (1002:679E / 106B:0126), Linux 7.2.5-omarchy, Mesa 26.2.2, amdgpu.
Results of the 300-frame 1080p60
macpro61-gpu test:02:00.006:00.0Both cards passed independent and concurrent tests with no faults or errors. Notable: on this unit the
02:00.0VCE engine sustained a fixed ~12 fps regardless of resolution/test pattern while06:00.0matched D500 throughput; this looks like a per-card VCE clock cap.vainfo/vulkaninfowere not installed, so those checks were skipped.