From: "Timothy B. Terriberry" <tterribe@xiph.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: how get drm-intel-next into a stable kernel
Date: Thu, 05 Aug 2010 11:47:29 -0700 [thread overview]
Message-ID: <4C5B0741.5060904@xiph.org> (raw)
In-Reply-To: <20100805175836.GA12571@kroah.com>
Any suggestions of patches to test for those of us still experiencing
eDP problems? I've seen a bunch fly by the list, but it's been unclear
to me which were supposed to address what issues, or how successful any
of them were.
I was able to get 2.6.34 to work on my Dell E6510 by reverting
885a5fb5b120a5c7e0b3baad7b0feb5a89f76c18 as suggested in
http://lists.freedesktop.org/archives/intel-gfx/2010-May/006948.html
This no longer works on 2.6.35 (black screen after starting X).
Even with that patch reverted on 2.6.34, I still ran into problems after
suspend: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/596080
I can hibernate as a work-around, but that often takes several minutes.
next prev parent reply other threads:[~2010-08-05 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 15:38 how get drm-intel-next into a stable kernel Sergio Monteiro Basto
2010-08-05 17:54 ` Jesse Barnes
2010-08-05 17:58 ` Greg KH
2010-08-05 18:47 ` Timothy B. Terriberry [this message]
2010-08-05 19:03 ` Brice Goglin
2010-08-05 19:47 ` Timothy B. Terriberry
2010-08-05 20:57 ` Sergio Monteiro Basto
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=4C5B0741.5060904@xiph.org \
--to=tterribe@xiph.org \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.