From: Eric Valette <eric.valette@free.fr>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Some user feedback on recent Intel chipset and 2.6.29 KMS
Date: Wed, 25 Feb 2009 20:10:17 +0100 [thread overview]
Message-ID: <49A59799.6050301@free.fr> (raw)
In-Reply-To: <49A52555.8070404@Free.fr>
Eric Valette wrote:
> Dave Airlie wrote:
>> See if the attached patch helps resume, there are also some other patches
>> queued for Linus in my drm-fixes tree. I sent the pull req earlier.
>>
>
> Thanks for the quick anwser.
>
> I will test the individual patch as soon as I get back home and report.
NB: the patch by itself missed an include for the prototype of the new
function called on resume.
Once I included the relevant drm include file it greatly improved resume
behavior: I managed to suspend at least once which has been impossible
for months (as soon as I entered an endless "catch up run" (fuite en
avant in french) due to a debian experimental libdrm package upgrade)).
However, it froze at second attempt.
> For the earlier pull, I will probably wait until its available in a
> 2.6.29-rc6-gitx and report. Do you want separate reports or testing the
> whole stuff?
I saw Linus integrated it so probably tomorrow...
Of course the "refresh" problem is still there as the patch is only for
resume path...
-- eric
next prev parent reply other threads:[~2009-02-25 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 10:19 Some user feedback on recent Intel chipset and 2.6.29 KMS Eric Valette
2009-02-25 10:37 ` Dave Airlie
2009-02-25 11:02 ` Eric Valette
2009-02-25 19:10 ` Eric Valette [this message]
2009-02-25 19:30 ` Eric Valette
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=49A59799.6050301@free.fr \
--to=eric.valette@free.fr \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.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