From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/crt: Do not rely upon the HPD presence pin
Date: Fri, 08 Jun 2012 23:23:10 +0100 [thread overview]
Message-ID: <1339194247_596313@CP5-2952> (raw)
In-Reply-To: <20120608222212.GI5761@phenom.ffwll.local>
On Sat, 9 Jun 2012 00:22:12 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, May 31, 2012 at 01:08:53PM +0100, Chris Wilson wrote:
> > Whilst most monitors do wire up the HPD presence pin, it seems quite a
> > few KVM do not. Therefore if we simply rely on the HPD pin being
> > asserted to indicate a connected monitor we fail miserable, so fall back
> > to performing a DCC query for the EDID.
> >
> > Reported-and-tested-by: Matthieu LAVIE <boiteamadmax@hotmail.com>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=50501
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Ok, this blew up ... Can you please resend, with Dave's suggestion for a
> rectified commit message & comment and with a check added such that we
> don't try to do load_detect on HAS_HOTPLUG machines - I guess it doesn't
> work too well.
I disagree, if we cannot trust the hw autodetection, then we know that
there are monitors/kvm that do not report an EDID and so we need to do
the whole shebang. Which will continue to annoy Linus since his machine
is behaving as expected given the circumstances.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-08 22:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 12:08 [PATCH] drm/i915/crt: Do not rely upon the HPD presence pin Chris Wilson
2012-05-31 12:50 ` Daniel Vetter
2012-05-31 13:34 ` Dave Airlie
2012-06-08 22:22 ` Daniel Vetter
2012-06-08 22:23 ` Chris Wilson [this message]
2012-06-10 17:04 ` Daniel Vetter
2012-06-10 19:17 ` Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2012-06-11 7:29 Daniel Vetter
2012-06-11 7:58 ` Chris Wilson
2012-06-11 8:40 ` Daniel Vetter
2012-06-11 9:46 ` Chris Wilson
2012-06-11 14:38 ` Daniel Vetter
2012-06-11 14:42 ` Chris Wilson
2012-06-11 19:00 ` Daniel Vetter
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=1339194247_596313@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox