On Thu, Feb 26, 2015 at 06:50:19PM -0800, Matt Roper wrote:
> On Wed, Feb 25, 2015 at 01:45:26PM +, Chris Wilson wrote:
> > The internal framebuffers we create to remap legacy cursor ioctls to
> > plane operations for the universal plane support shouldn't be linke to
> > the file like normal us
On Thu, Feb 26, 2015 at 06:50:19PM -0800, Matt Roper wrote:
> On Wed, Feb 25, 2015 at 01:45:26PM +, Chris Wilson wrote:
> > The internal framebuffers we create to remap legacy cursor ioctls to
> > plane operations for the universal plane support shouldn't be linke to
> > the file like normal us
On Fri, Feb 27, 2015 at 12:15:16PM +0100, Daniel Vetter wrote:
> On Thu, Feb 26, 2015 at 06:50:19PM -0800, Matt Roper wrote:
> > On Wed, Feb 25, 2015 at 01:45:26PM +, Chris Wilson wrote:
> > > The internal framebuffers we create to remap legacy cursor ioctls to
> > > plane operations for the un
On Wed, Feb 25, 2015 at 01:45:26PM +, Chris Wilson wrote:
> The internal framebuffers we create to remap legacy cursor ioctls to
> plane operations for the universal plane support shouldn't be linke to
> the file like normal userspace framebuffers. This bug goes back to the
> original universal
The internal framebuffers we create to remap legacy cursor ioctls to
plane operations for the universal plane support shouldn't be linke to
the file like normal userspace framebuffers. This bug goes back to the
original universal cursor plane support introduced in
commit 161d0dc1dccb17ff7a38f462c7