On Fri 15 Sep 2017, zhoucm1 wrote:
>
>
> On 2017年09月14日 07:03, Chad Versace wrote:
> > From: Chad Versace
> >
> > This implementation is correct (afaict), but takes two shortcuts
> > regarding the import/export of Android sync fds.
> >
> >Shortcut 1. When Android calls vkAcquireImageANDROI
On 2017年09月14日 07:03, Chad Versace wrote:
From: Chad Versace
This implementation is correct (afaict), but takes two shortcuts
regarding the import/export of Android sync fds.
Shortcut 1. When Android calls vkAcquireImageANDROID to import a sync
fd into a VkSemaphore or VkFence, the dri
On Thu 14 Sep 2017, Tapani Pälli wrote:
>
>
> On 09/14/2017 08:51 AM, Tapani Pälli wrote:
> >
> >
> > On 09/14/2017 02:03 AM, Chad Versace wrote:
> > > From: Chad Versace
> > >
> > > This implementation is correct (afaict), but takes two shortcuts
> > > regarding the import/export of Android
On 09/14/2017 08:51 AM, Tapani Pälli wrote:
On 09/14/2017 02:03 AM, Chad Versace wrote:
From: Chad Versace
This implementation is correct (afaict), but takes two shortcuts
regarding the import/export of Android sync fds.
Shortcut 1. When Android calls vkAcquireImageANDROID to import a
On 09/14/2017 02:03 AM, Chad Versace wrote:
From: Chad Versace
This implementation is correct (afaict), but takes two shortcuts
regarding the import/export of Android sync fds.
Shortcut 1. When Android calls vkAcquireImageANDROID to import a sync
fd into a VkSemaphore or VkFence, the d
From: Chad Versace
This implementation is correct (afaict), but takes two shortcuts
regarding the import/export of Android sync fds.
Shortcut 1. When Android calls vkAcquireImageANDROID to import a sync
fd into a VkSemaphore or VkFence, the driver instead simply blocks on
the sync fd, then