From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ivan Bulatovic <combuster@gmx.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
jbarnes@virtuousgeek.org, eric@anholt.net
Subject: Re: i915: 2.6.36-rc2 wrong resolution on gdm start
Date: Tue, 24 Aug 2010 09:50:29 +0100 [thread overview]
Message-ID: <89kc63$hrqmar@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1282638912.2191.17.camel@localhost.localdomain>
On Tue, 24 Aug 2010 10:35:12 +0200, Ivan Bulatovic <combuster@gmx.com> wrote:
> Above patches didn't help when applied to 2.6.36-rc2.
Would be useful to double check reverting the bad commit helps.
> I'm going to compare dmesg between 2.6.35.3 and 2.6.36-rc2 with
> drm.debug=0x6. Thanks,
Aye that would be a useful check.
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-08-24 8:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 1:00 i915: 2.6.36-rc2 wrong resolution on gdm start Ivan Bulatovic
2010-08-24 7:49 ` Chris Wilson
2010-08-24 8:35 ` Ivan Bulatovic
2010-08-24 8:50 ` Chris Wilson [this message]
2010-08-24 9:12 ` Ivan Bulatovic
2010-08-24 9:21 ` [PATCH] drm/i915/tv: Flush register writes before sleeping Chris Wilson
2010-08-24 11:03 ` Ivan Bulatovic
2010-08-24 15:11 ` [PATCH] drm/i915/tv: After disabling the pipe, use wait_for_vblank_off() Chris Wilson
2010-08-24 21:08 ` Ivan Bulatovic
2010-08-24 21:52 ` Chris Wilson
2010-08-24 23:00 ` Ivan Bulatovic
2010-08-24 23:04 ` Ivan Bulatovic
2010-08-24 23:05 ` Jesse Barnes
2010-08-24 23:06 ` Ivan Bulatovic
2010-08-25 8:15 ` Sitsofe Wheeler
2010-08-25 9:17 ` Ivan Bulatovic
2010-08-25 9:31 ` Ivan Bulatovic
2010-08-25 9:51 ` Kan-Ru Chen
2010-08-29 11:29 ` i915: 2.6.36-rc2 wrong resolution on gdm start Pekka Enberg
2010-08-29 13:37 ` Sitsofe Wheeler
2010-08-24 8:54 ` Pekka Enberg
2010-08-29 12:59 ` Maciej Rutecki
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='89kc63$hrqmar@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=combuster@gmx.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--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