[PATCH 1/2] dxgi/tests: Add test for enumerating display adapters using SetupAPI.

Józef Kucia joseph.kucia at gmail.com
Tue Dec 4 09:43:20 CST 2018


Thanks for starting the discussion.

On Mon, Dec 3, 2018 at 8:43 PM Zebediah Figura <z.figura12 at gmail.com> wrote:
> Just to sort of continue the discussion here, what are we imagining to
> be responsible for creating display devices (and hence allocating LUIDs)?

I don't really know at this point. We talked about it a bit on IRC,
but there is no consensus yet on what should be responsible for
creating display devices and allocating LUIDs. I imagine Wine graphics
driver should be involved since we need to enumerate available Vulkan
physical devices.

The patch was submitted mainly to show a potential storage for display
adapter LUIDs. We would like to expose stable LUIDs in OpenGL [1] and
Vulkan [2]. When we have stable LUIDs in OpenGL and Vulkan we will be
able to match OpenGL and Vulkan devices, and expose stable LUIDs in
d3d9 and dxgi.

[1] - See DEVICE_LUID_EXT in
https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_external_objects_win32.txt.
[2] - https://www.khronos.org/registry/vulkan/specs/1.1-extensions/man/html/VkPhysicalDeviceIDProperties.html



More information about the wine-devel mailing list