ENHANCEMENT: Remove VkSurfaceKHR and SwapChain Extension code about lucurious HOT 2 OPEN

The Vk_KHR_display extension isn't going to be useful.

To my knowledge I may be wrong there is no way to import gmb_bo directly into Vulkan. If the wayland display protocol is used one can create the underlying wl_buffer with gbm and import the wl_buffer into Vulkan to get desired content. But i'm not using any display server protocol.

The VK_EXT_image_drm_format_modifier extension is still needed.

Thinking I should create gbm_bo's and gather plane FD's/GEM handles to assign plane info to a VkImageDrmFormatModifierExplicitCreateInfoEXT structure. Then create a VkImage object with this structures address assigned to the pNext chain of the VkImageCreateInfo.

The VK_KHR_external_memory extension may be more useful.

from lucurious.

How I retrieve DMA BUF FD

1. Create gbm_bo
2. Retrieve number of GEM buffers with gbm_bo_get_plane_count. GEM buffers are wrapped by KMS framebuffers which contain metadata.
3. Retrieve the GEM name (u32) with gbm_bo_get_handle_for_plane
4. Create a prime fd from GEM name (u32) via struct drm_prime_handle prime_request and ioctl(2)
5. Once one has a prime fd [DMA-BUF fd] extensions needed afterwards

• VK_KHR_external_memory
• VK_KHR_external_memory_fd
• VK_EXT_external_memory_dma_buf
• VK_EXT_image_drm_format_modifier [Still not in Mesa]

from lucurious.