public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org, mjg@redhat.com, eric@anholt.net,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: no video output after suspend after "drm/i915: force mode set at lid open time"
Date: Wed, 04 Nov 2009 21:16:31 +0100	[thread overview]
Message-ID: <4AF1E11F.6000404@gmail.com> (raw)
In-Reply-To: <20091104111958.1b9c738e@jbarnes-piketon>

Jesse Barnes ha scritto:
> On Sat, 31 Oct 2009 14:46:43 +0100
> Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com> wrote:
>>> Sorry for taking so long to respond. Anyway latest Linus' git
>>> master with reverted c1c7af60892070e4b82ad63bbfb95ae745056de0 , per
>>> attached patch, does not fix the issue for me. Please note that
>>> just reverting the commit does not compile because of an added user
>>> of acpi_lid_open() which requires acpi/button.h which has been
>>> added in 7121413f2accf14cf05b38539fb7a8be77543370. Will try to
>>> revert that too.
>> Sorry, that commit just change that line, it does not add the 
>> acpi_lid_open() call.
> 
> Linus's tree has another change which might help:
> 
> commit c9354c85c1c7bac788ce57d3c17f2016c1c45b1d
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Mon Nov 2 09:29:55 2009 -0800
> 
>     i915: fix intel graphics suspend breakage due to resume/lid event
>     confusion
> 
> Have you tried a tree with it included yet?

Sure, i tested 2.6.32-rc6 and latest Linus' git 
91d3f9bacdb4950d2f79fe2ba296aa249f60d06c which has latest pull from drm 
tree.

Btw, does anybody know how to update bugzilla by email? Can't find it 
mentioned anywhere.

thanks,
riccardo

      reply	other threads:[~2009-11-04 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 20:57 no video output after suspend after "drm/i915: force mode set at lid open time" Riccardo Magliocchetti
2009-10-26  1:52 ` Peter Stuge
2009-10-26 16:02   ` Jesse Barnes
2009-10-26 19:28     ` Peter Stuge
2009-10-26 19:39       ` Rafael J. Wysocki
2009-10-26 19:42         ` Peter Stuge
2009-10-26 20:00           ` Rafael J. Wysocki
2009-10-26 16:05 ` Jesse Barnes
2009-10-27 21:21   ` Riccardo Magliocchetti
2009-10-27 21:26     ` Jesse Barnes
2009-10-31 13:42       ` Riccardo Magliocchetti
2009-10-31 13:46         ` Riccardo Magliocchetti
2009-11-04 19:19           ` Jesse Barnes
2009-11-04 20:16             ` Riccardo Magliocchetti [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AF1E11F.6000404@gmail.com \
    --to=riccardo.magliocchetti@gmail.com \
    --cc=eric@anholt.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox