On Sun, 19 Aug 2012 21:12:49 +0200 Daniel Vetter <daniel.vet...@ffwll.ch> wrote:
> Afaict this has been used for two things: > - To prevent the crtc enable code from being run twice. We have now > intel_crtc->active to track this in a more precise way. > - To ensure the code copes correctly with the unknown hw state after > boot and resume. Thanks to the hw state readout and sanitize code we > have now a better way to handle this. > > The only thing it still does is complicate our modeset state space. > > Having outlived its usefullness, let it just die. Yay! Reviewed-by: Jesse Barnes <jbar...@virtuousgeek.org> -- Jesse Barnes, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
