On Tue, Feb 19, 2013 at 04:18:07PM +0100, Thierry Reding wrote:
> When updating a plane, the DRM core always sets the plane's framebuffer
> to NULL. This in turn will cause the reference count on the plane's
> active framebuffer to become unbalanced because on the next update, the
> old framebuffer
On Tue, Feb 19, 2013 at 05:32:56PM +0200, Ville Syrj?l? wrote:
> On Tue, Feb 19, 2013 at 04:18:07PM +0100, Thierry Reding wrote:
> > When updating a plane, the DRM core always sets the plane's framebuffer
> > to NULL. This in turn will cause the reference count on the plane's
> > active framebuffer
When updating a plane, the DRM core always sets the plane's framebuffer
to NULL. This in turn will cause the reference count on the plane's
active framebuffer to become unbalanced because on the next update, the
old framebuffer will be NULL.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_
On Tue, Feb 19, 2013 at 05:32:56PM +0200, Ville Syrjälä wrote:
> On Tue, Feb 19, 2013 at 04:18:07PM +0100, Thierry Reding wrote:
> > When updating a plane, the DRM core always sets the plane's framebuffer
> > to NULL. This in turn will cause the reference count on the plane's
> > active framebuffer
On Tue, Feb 19, 2013 at 04:18:07PM +0100, Thierry Reding wrote:
> When updating a plane, the DRM core always sets the plane's framebuffer
> to NULL. This in turn will cause the reference count on the plane's
> active framebuffer to become unbalanced because on the next update, the
> old framebuffer
When updating a plane, the DRM core always sets the plane's framebuffer
to NULL. This in turn will cause the reference count on the plane's
active framebuffer to become unbalanced because on the next update, the
old framebuffer will be NULL.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_
