-
Show log
Commit
-
Hash : 801993bc
Author :
Date : 2025-01-18T21:48:41
handle Qualcomm's mixed vendor IDs This is a weird situation. Up until Qualcomm had a native Vulkan driver for Windows (with the Snapdragon X series chips), the only vendor ID observable on Windows was 0x4D4F4351. This was reported through DXGI, device manager, etc. But with their native Vulkan driver, they now report 0x5143 as well: VkPhysicalDeviceProperties: --------------------------- apiVersion = 1.3.295 (4206887) driverVersion = 0.807.0 (2150789120) vendorID = 0x5143 deviceID = 0x36334330 deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU deviceName = Qualcomm(R) Adreno(TM) X1-85 GPU pipelineCacheUUID = 0eba4509-4351-0000-0000-010c05430000 And yet, DXGI still reports 0x4D4F4351. Cool, huh? Let's teach IsQualcomm to understand both vendor IDs to ensure the device is correctly detected as a tile-based renderer in the Vulkan backend. Bug: angleproject:390866623 Change-Id: I9170c30262ace269498f066e922a279c7e981de6 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/6183621 Reviewed-by: Geoff Lang <geofflang@chromium.org> Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org> Commit-Queue: Geoff Lang <geofflang@chromium.org> Auto-Submit: Steven Noonan <steven@uplinklabs.net>
-
Files
- SystemInfo.cpp
- SystemInfo.h
- SystemInfo_android.cpp
- SystemInfo_apple.mm
- SystemInfo_fuchsia.cpp
- SystemInfo_internal.h
- SystemInfo_ios.cpp
- SystemInfo_libpci.cpp
- SystemInfo_linux.cpp
- SystemInfo_macos.mm
- SystemInfo_unittest.cpp
- SystemInfo_vulkan.cpp
- SystemInfo_vulkan.h
- SystemInfo_win.cpp
- SystemInfo_x11.cpp
