Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vk: Fix detection of RADV on get_driver_vendor() #14432

Merged
merged 1 commit into from Aug 5, 2023
Merged

Conversation

AniLeo
Copy link
Member

@AniLeo AniLeo commented Aug 5, 2023

Since Mesa 22.2.0 (2022-09-21), commit f06da59fd75d7ce7708d159753fcdbc11de16f9e, the deviceName property has included the name of the GPU, thus invalidating our previous method of detecting RADV as a driver vendor.

Because the AMD check looks for "Radeon" and comes before the RADV one, RADV drivers started wrongly being detected as AMD proprietary. The fix is to simply do the RADV check before the AMD one.

Examples:

Before: "AMD RADV NAVY_FLOUNDER"
After: "AMD Radeon RX 6700M (RADV NAVI22)"

Before: "AMD RADV RENOIR"
After: "AMD Radeon Graphics (RADV RENOIR)"

Since Mesa 22.2.0 (2022-09-21), commit 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11027/diffs?commit_id=f06da59fd75d7ce7708d159753fcdbc11de16f9e, 
the deviceName property has included the name of the GPU, thus 
invalidating our previous method of detecting RADV as a driver vendor

Before: "AMD RADV NAVY_FLOUNDER"
After: "AMD Radeon RX 6700M (RADV NAVI22)"

Before: "AMD RADV RENOIR"
After: "AMD Radeon Graphics (RADV RENOIR)"
@AniLeo AniLeo added Bugfix Render: Vulkan Driver: RADV (Mesa) Open-source AMD Vulkan Mesa driver labels Aug 5, 2023
@AniLeo AniLeo requested a review from kd-11 August 5, 2023 21:53
@AniLeo AniLeo merged commit 6672499 into RPCS3:master Aug 5, 2023
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugfix Driver: RADV (Mesa) Open-source AMD Vulkan Mesa driver Render: Vulkan
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants