History

hwcontext_vulkan: stricter semaphore number requirements

Always require one semaphore per sw_format plane. This is what the implementation uses and relies upon throughout. This was a leftover from an earlier revision that was never needed.

Lynne committed 4 years ago

Commit 07477681 parent 83fe2821 file · +4 −6Browse files

Unified · Split

libavutil/hwcontext_vulkan.h+4−6
@@ -241,12 +241,10 @@ typedef struct AVVkFrame { · 240 unmodified lines
241 VkImageLayout layout[AV_NUM_DATA_POINTERS];241 VkImageLayout layout[AV_NUM_DATA_POINTERS];
242 242
243 /**243 /**
244 * Synchronization timeline semaphores. Must not be freed manually.244 * Synchronization timeline semaphores, one for each sw_format plane.
245 * Must be waited on at every submission using the value in sem_value,245 * Must not be freed manually. Must be waited on at every submission using
246 * and must be signalled at every submission, using an incremented value.246 * the value in sem_value, and must be signalled at every submission,
247 *247 * using an incremented value.
248 * Could be less than the amount of images: either one per VkDeviceMemory
249 * or one for the entire frame. All others will be set to VK_NULL_HANDLE.
250 */248 */
251 VkSemaphore sem[AV_NUM_DATA_POINTERS];249 VkSemaphore sem[AV_NUM_DATA_POINTERS];
252 250

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t