On Fri, 7 Nov 2014 18:41:16 +0100
Daniel Vetter wrote:
> On Tue, Nov 04, 2014 at 03:29:57PM +0100, Daniel Vetter wrote:
> > Fastboot in its current incarnation assumes that the pfit isn't
> > relevatn for the state and that it can be disabled without
> > restarting the crtc. Unfortunately that's
On Tue, Nov 04, 2014 at 03:29:57PM +0100, Daniel Vetter wrote:
> Fastboot in its current incarnation assumes that the pfit isn't
> relevatn for the state and that it can be disabled without restarting
> the crtc. Unfortunately that's not the case on gen2/3 - it upsets the
> hw and results in a blac
Dear Daniel,
thank you for the support in #intel-...@irc.freenode.net and the patch.
As already commented in the bug report #84682, there are some typos.
Am Dienstag, den 04.11.2014, 15:29 +0100 schrieb Daniel Vetter:
> Fastboot in its current incarnation assumes that the pfit isn't
> relevatn f
Fastboot in its current incarnation assumes that the pfit isn't
relevatn for the state and that it can be disabled without restarting
the crtc. Unfortunately that's not the case on gen2/3 - it upsets the
hw and results in a black screen.
Worse, the way the current fastboot hack is structure we can