On Thu, Apr 25, 2013 at 05:24:19PM +0300, Mika Kuoppala wrote:
> Daniel Vetter writes:
>
> > This does duplicate the logic in intel_crtc_mode_get a bit, but the
> > issue is that we also should handle interlace modes and other insanity
> > correctly.
> >
> > Hence I've opted for a sligthly more e
Daniel Vetter writes:
> This does duplicate the logic in intel_crtc_mode_get a bit, but the
> issue is that we also should handle interlace modes and other insanity
> correctly.
>
> Hence I've opted for a sligthly more elaborate route where we first
> read out the crtc timings for the adjusted mo
This does duplicate the logic in intel_crtc_mode_get a bit, but the
issue is that we also should handle interlace modes and other insanity
correctly.
Hence I've opted for a sligthly more elaborate route where we first
read out the crtc timings for the adjusted mode, and then optionally
(not sure i
