diff options
| author | Lynne <[email protected]> | 2020-03-12 18:01:07 +0000 |
|---|---|---|
| committer | Lynne <[email protected]> | 2020-03-12 18:16:11 +0000 |
| commit | 501bd57bdbc488db93c95d40682ef0b4f01ccec5 (patch) | |
| tree | a84a2b81ca301a8a1fd08f00a42b431a3c81171d /doc/examples/qsvdec.c | |
| parent | 9086af2a0a590c7f576b72379d1708392cd96d5c (diff) | |
hwcontext_vulkan: initialize semaphores of DMABUF imports
There was a recent change in Intel's driver that triggered a driver-internal
error if the semaphore given to the command buffer wasn't initialized.
Given that the specifications require the semaphore to be initialized,
this is within spec. Unlike what's causing it in the first place, which is
that there are no ways to extract/import dma sync objects from DMABUFs,
so we must leave our semaphores bare.
Diffstat (limited to 'doc/examples/qsvdec.c')
0 files changed, 0 insertions, 0 deletions