On Fri, Jun 8, 2012 at 3:56 PM, Erik Gilling konk...@android.com wrote:
I guess my other thought is that implicit vs explicit is not
mutually exclusive, though I'd guess there'd be interesting
deadlocks to have to debug if both were in use _at the same
time_. :-)
I think this is an approach
On Sat, Jun 9, 2012 at 12:22 AM, Erik Gilling konk...@android.com wrote:
The current linux graphics stack does not allow synchronization
between the GPU and a camera/video decoder. When we've seen people
try to support this behind the scenes, they get it wrong and introduce
bugs that can take
On Thu, Jun 7, 2012 at 4:35 AM, Tom Cooksey tom.cook...@arm.com wrote:
The alternate is to not associate sync objects with buffers and
have them be distinct entities, exposed to userspace. This gives
userpsace more power and flexibility and might allow for use-cases
which an implicit
On Fri, Jun 08, 2012 at 01:56:05PM -0700, Erik Gilling wrote:
On Thu, Jun 7, 2012 at 4:35 AM, Tom Cooksey tom.cook...@arm.com wrote:
The alternate is to not associate sync objects with buffers and
have them be distinct entities, exposed to userspace. This gives
userpsace more power and
On Fri, Jun 8, 2012 at 2:42 PM, Daniel Vetter dan...@ffwll.ch wrote:
I think this is an approach worth investigating. I'd like a way to
either opt out of implicit sync or have a way to check if a dma-buf
has an attached fence and detach it. Actually, that could work really
well. Consider:
