On Fri, Jun 07, 2013 at 09:32:33PM +0200, Daniel Vetter wrote:
> On Fri, Jun 7, 2013 at 9:14 PM, Chris Wilson wrote:
> > On Fri, Jun 07, 2013 at 09:10:23PM +0200, Daniel Vetter wrote:
> >> On Fri, Jun 07, 2013 at 01:47:41PM +0100, Chris Wilson wrote:
> >> > + if (intel_crtc_set_c
On Fri, Jun 7, 2013 at 9:14 PM, Chris Wilson wrote:
> On Fri, Jun 07, 2013 at 09:10:23PM +0200, Daniel Vetter wrote:
>> On Fri, Jun 07, 2013 at 01:47:41PM +0100, Chris Wilson wrote:
>> > + if (intel_crtc_set_config(&set))
>> > + __intel_set_mode(crtc, &c
On Fri, Jun 07, 2013 at 09:10:23PM +0200, Daniel Vetter wrote:
> On Fri, Jun 07, 2013 at 01:47:41PM +0100, Chris Wilson wrote:
> > + if (intel_crtc_set_config(&set))
> > + __intel_set_mode(crtc, &crtc->mode,
> > +
On Fri, Jun 07, 2013 at 01:47:41PM +0100, Chris Wilson wrote:
> On random machines, the BIOS changes the hardware state of the display
> when it detects a lid event. In return, we have to then do a forced
> restore of the users requested configuration as soon as we handle the
> lid event. Currently
On Fri, Jun 7, 2013 at 2:47 PM, Chris Wilson wrote:
> On random machines, the BIOS changes the hardware state of the display
> when it detects a lid event. In return, we have to then do a forced
> restore of the users requested configuration as soon as we handle the
> lid event. Currently, this is
On random machines, the BIOS changes the hardware state of the display
when it detects a lid event. In return, we have to then do a forced
restore of the users requested configuration as soon as we handle the
lid event. Currently, this is done by calling the lowlevel CRTC
configuration functions di
