diff options
| author | Eric Anholt <[email protected]> | 2018-07-09 12:41:46 -0700 |
|---|---|---|
| committer | Eric Anholt <[email protected]> | 2018-07-20 11:11:29 -0700 |
| commit | a221f9709efeaf0ac901c7b0568e8aa311aa1b96 (patch) | |
| tree | 2a63be1670bbca761fbc141936eb86afeb05ddde /docs/relnotes/10.2.9.html | |
| parent | fc28692a5af22754818e2eda20409f9502daa088 (diff) | |
v3d: Fix incorrect handling of two fences created back-to-back.
Recreating our context's syncobj with ALREADY_SIGNALED meant that if you
created two fences in a row, then waiting on the second would succeed
immediately. Instead, export a sync file in the gallium fence (since we
don't have a syncobj clone ioctl), and just create a new syncobj to wait
on whenever we need to.
Noticed while debugging
dEQP-GLES3.functional.fence_sync.client_wait_sync_finish
Diffstat (limited to 'docs/relnotes/10.2.9.html')
0 files changed, 0 insertions, 0 deletions