-
Notifications
You must be signed in to change notification settings - Fork 192
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
extensions/ext: Add VK_EXT_acquire_drm_display #668
Conversation
drm_fd: i32, | ||
connector_id: u32, | ||
) -> VkResult<vk::DisplayKHR> { | ||
let mut display = mem::MaybeUninit::uninit(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've only sparsely used MaybeUninit
before (only ever in VK_KHR_display
), and only with zeroed()
instead of uninit()
.
Doesn't seem like there's any harm in doing that here, so I'm willing to try that out (and hopefully schedule to replace more MaybeUninit::zeroed()
/mem::zeroed()
/default()
calls at some point).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the other extension implementations by example, making this super easy to review!
Co-authored-by: Aidan Prangnell <[email protected]>
Note that KhronosGroup/Vulkan-ValidationLayers#4136 prevents the use of
vkGetDrmDisplayEXT
while usingVK_LAYER_KHRONOS_validation
.