From: Chris Wilson <chris@chris-wilson.co.uk>
To: Keith Packard <keithp@keithp.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/crt: Explicitly return false if connected to a digital monitor
Date: Mon, 04 Apr 2011 16:25:27 +0100 [thread overview]
Message-ID: <b7da2f$qvddbq@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <yunfwpyaw95.fsf@aiko.keithp.com>
On Mon, 04 Apr 2011 08:09:42 -0700, Keith Packard <keithp@keithp.com> wrote:
> On Mon, 4 Apr 2011 07:26:45 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> > Rather than proceed on to the next test, return the result from
> > detecting a connection but to a digital panel and include some debug
> > output as to why.
>
> I'm worried that this will falsely reject some monitors with broken EDID
> information.
This doesn't change the nature of the test, just adds a debug
message so that we explain why it was rejected. Vital information should
anyone report a bug with a connected VGA monitor.
This is another case where we are damned if we do and damned if we don't.
Some hardware requires us to differentiate between VGA/DVI connections on
the same i2c wire and the rejection here was originally added to enable us
to function correctly on such a machine.
As far as broken EDIDs go, there are plenty of bugs to go around.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-04 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 6:26 [PATCH 1/2] drm/i915/crt: Remove 0xa0 probe for CRT Chris Wilson
2011-04-04 6:26 ` [PATCH 2/2] drm/i915/crt: Explicitly return false if connected to a digital monitor Chris Wilson
2011-04-04 15:09 ` Keith Packard
2011-04-04 15:25 ` Chris Wilson [this message]
2011-04-04 16:27 ` Keith Packard
2011-04-04 15:08 ` [PATCH 1/2] drm/i915/crt: Remove 0xa0 probe for CRT Keith Packard
2011-04-04 15:29 ` Chris Wilson
2011-04-04 16:26 ` Keith Packard
2011-04-05 0:19 ` Dave Airlie
2011-04-05 1:04 ` Keith Packard
2011-04-05 9:18 ` Chris Wilson
2011-04-05 1:57 ` Keith Packard
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='b7da2f$qvddbq@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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