From: "Wouter M. Koolen" <W.M.Koolen-Wijkstra@cwi.nl>
To: "Wouter M. Koolen" <W.M.Koolen-Wijkstra@cwi.nl>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Dave Airlie <airlied@gmail.com>,
intergalactic.anonymous@gmail.com, len.brown@intel.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Barnes, Jesse" <jbarnes@virtuousgeek.org>,
"Wilson, Chris" <chris.wilson@intel.com>
Subject: Re: [3.4 regression] [bisected] DisplayPort fails to come on
Date: Thu, 14 Jun 2012 18:14:43 +0100 [thread overview]
Message-ID: <4FDA1C03.3020404@cwi.nl> (raw)
In-Reply-To: <4FD9F9B0.9030204@cwi.nl>
On 06/14/2012 03:48 PM, Wouter M. Koolen wrote:
> In the mean while I will redo the bisect.
Hi guys,
I did a bisect on the actual problem (and not on the maybe-related
second error message). It results in
092945e11c5b84f66dd08f0b87fb729715d377bc:
Author: Adam Jackson <ajax@redhat.com> 2011-07-26 20:39:45
Committer: Daniel Vetter <daniel.vetter@ffwll.ch> 2012-01-17 15:46:56
Parent: 6919132e7a307b1f181d7655b3ef64cc7581a5ef (drm/i915/dp: Tweak
auxch clock divider for PCH)
Branches: linux-3.4.y, remotes/origin/linux-3.4.y, remotes/origin/master
Follows: v3.2-rc6
Precedes: v3.4-rc1
drm/i915/dp: Use auxch precharge value of 5 everywhere
The default in the Sandybridge docs is 5, as on Ironlake, and I have no
reason to believe 3 would work any better.
Signed-off-by: Adam Jackson <ajax@redhat.com>
Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
I guess there is your reason for 3 :)
Any advice on how to proceed would be very helpful.
Cheers,
Wouter
next prev parent reply other threads:[~2012-06-14 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 13:26 [3.4 regression] [bisected] DisplayPort fails to come on Wouter M. Koolen
2012-06-14 14:00 ` Dave Airlie
2012-06-14 14:05 ` Daniel Vetter
2012-06-14 14:48 ` Wouter M. Koolen
2012-06-14 17:14 ` Wouter M. Koolen [this message]
2012-06-14 17:27 ` Daniel Vetter
2012-06-14 18:29 ` Wouter M. Koolen
2012-06-14 21:52 ` Brown, Len
2012-06-15 8:23 ` Wouter M. Koolen
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=4FDA1C03.3020404@cwi.nl \
--to=w.m.koolen-wijkstra@cwi.nl \
--cc=airlied@gmail.com \
--cc=chris.wilson@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intergalactic.anonymous@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=len.brown@intel.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