On Fri, May 16, 2014 at 06:53:52PM +0200, Daniel Vetter wrote:
> On Fri, May 16, 2014 at 05:36:59PM +0100, Chris Wilson wrote:
> > Extremely unlikely to ever be required, but BIOSes do like to attack in
> > unexpected ways.
> > 
> > Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk>
> > ---
> >  drivers/gpu/drm/i915/intel_display.c |    2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_display.c 
> > b/drivers/gpu/drm/i915/intel_display.c
> > index a943ea7..5583e9b 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -11817,6 +11817,8 @@ static void intel_sanitize_crtc(struct intel_crtc 
> > *crtc)
> >     /* Adjust the state of the output pipe according to whether we
> >      * have active connectors/encoders. */
> >     intel_crtc_update_dpms(&crtc->base);
> > +   intel_crtc_update_cursor(crtc,
> > +                            intel_crtc->active && intel_crtc->cursor_bo);
> 
> Should we do this for sprite planes, too? That way it would be nice fodder
> for Matt to clean up later on ;-)

* pokes Ville ;-)
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to