From: Chris Wilson <chris@chris-wilson.co.uk>
To: Keith Packard <keithp@keithp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: prefer wide & slow to fast & narrow in DP configs
Date: Fri, 22 Jun 2012 18:53:01 +0100 [thread overview]
Message-ID: <1340387615_42474@CP5-2952> (raw)
In-Reply-To: <86a9zvqm7t.fsf@sumi.keithp.com>
On Fri, 22 Jun 2012 10:40:22 -0700, Keith Packard <keithp@keithp.com> wrote:
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > On Thu, 21 Jun 2012 18:13:19 -0700, Keith Packard <keithp@keithp.com> wrote:
>
> > It was structured to minimise lane count because certain chipsets did
> > not wire up all the lanes, right? Is that still relevant as we are using
> > the advertised max_lane_count from the DPCD now?
>
> We've always used the max_lane_count from dpcd; has there been some
> recent change that fixed usage of that? What I recall is one acer laptop
> that advertised 4 lanes but had only wired up two of them.
The only recentish change was your
commit 9a10f401a401ca69c6537641c8fc0d6b57b5aee8
Author: Keith Packard <keithp@keithp.com>
Date: Wed Nov 2 13:03:47 2011 -0700
drm/i915: Use DPCD value for max DP lanes.
The BIOS VBT value for an eDP panel has been shown to be incorrect on
one machine, and we haven't found any machines where the DPCD value
was wrong, so we'll use the DPCD value everywhere.
We can but hope that no manufacturer lies in the DPCD.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-22 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 22:13 [PATCH] drm/i915: prefer wide & slow to fast & narrow in DP configs Jesse Barnes
2012-06-22 1:13 ` Keith Packard
2012-06-22 9:05 ` Chris Wilson
2012-06-22 14:21 ` Adam Jackson
2012-06-22 16:29 ` Jesse Barnes
2012-06-22 17:42 ` Keith Packard
2012-06-22 17:40 ` Keith Packard
2012-06-22 17:53 ` Chris Wilson [this message]
2012-07-04 7:42 ` Daniel Vetter
2012-08-06 0:12 ` [3.2.y, 3.4.y, 3.5.y] " Jonathan Nieder
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=1340387615_42474@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
/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