On Tue, Jul 29, 2014 at 04:46:11PM -0700, Matt Roper wrote:
On Tue, Jul 29, 2014 at 11:32:19PM +0200, Daniel Vetter wrote:
Atomic implemenations for legacy ioctls must be able to drop locks.
Which doesn't cause havoc since we only do that while constructing
the new state, so no driver or
Atomic implemenations for legacy ioctls must be able to drop locks.
Which doesn't cause havoc since we only do that while constructing
the new state, so no driver or hardware state change has happened.
The only troubling bit is the fb refcounting the core does - if
someone else has snuck in then
On 30 July 2014 07:32, Daniel Vetter daniel.vet...@ffwll.ch wrote:
Atomic implemenations for legacy ioctls must be able to drop locks.
Which doesn't cause havoc since we only do that while constructing
the new state, so no driver or hardware state change has happened.
The only troubling bit
On Tue, Jul 29, 2014 at 11:32:19PM +0200, Daniel Vetter wrote:
Atomic implemenations for legacy ioctls must be able to drop locks.
Which doesn't cause havoc since we only do that while constructing
the new state, so no driver or hardware state change has happened.
The only troubling bit is
