[Bug 104865] Mapping a DMABUF frame as a VkImage and then copying/blitting the image to another produces blank output

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jan 30 20:23:13 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=104865

--- Comment #1 from Jason Ekstrand <jason at jlekstrand.net> ---
I think the problem you are running into is that VK_EXT_external_memory_dma_buf
is purely a memory sharing mechanism and doesn't actually provide needed APIs
for importing images.  That will be covered by VK_EXT_image_drm_format_modifier
which has not yet been finalized.  It's definitely in-progress and we're hoping
to get things nailed down very soon.

In the mean time, what you're trying to do is still possible, you just have to
go about it differently.  Instead of creating a linear VkImage on the DMABUF,
create a VkBuffer and then use vkCmdCopyBufferToImage and provide the image
stride using bufferRowLength.  The current Vulkan WSI code in mesa already does
this internally for cross-GPU sharing via prime.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180130/2d15bc85/attachment.html>


More information about the intel-3d-bugs mailing list