From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tino Keitel <tino.keitel@tikei.de>, linux-kernel@vger.kernel.org
Subject: Re: DVI/EDID broken with Intel i945 graphics and 2.6.37-rc2
Date: Wed, 17 Nov 2010 10:20:09 +0000 [thread overview]
Message-ID: <b9dded$h40vqf@orsmga002.jf.intel.com> (raw)
In-Reply-To: <20101116184914.GA15794@mac.home>
On Tue, 16 Nov 2010 19:49:14 +0100, Tino Keitel <tino.keitel@tikei.de> wrote:
> Hi,
>
> 2.6.37-rc2 doesn't seem to detect the LCD connected via DVI on my Mac
> mini Core2 Duo with i945 graphics:
Hmm, sounds like fallout from detection of the VGA connection on the shared
GPIO wire.
Does this help?
diff --git a/drivers/gpu/drm/i915/intel_sdvo.c b/drivers/gpu/drm/i915/intel_sdvo
index de158b7..ec32ceb 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -1327,11 +1327,8 @@ intel_analog_is_connected(struct drm_device *dev)
if (!analog_connector)
return false;
- if (analog_connector->funcs->detect(analog_connector, false) ==
- connector_status_disconnected)
- return false;
-
- return true;
+ return analog_connector->funcs->detect(analog_connector, false) ==
+ connector_status_connected;
}
An alternative is to force detection, ie change the detect(analog, false)
to true.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-17 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 18:49 DVI/EDID broken with Intel i945 graphics and 2.6.37-rc2 Tino Keitel
2010-11-17 10:20 ` Chris Wilson [this message]
2010-11-17 12:02 ` Tino Keitel
2010-11-17 20:01 ` Tino Keitel
2010-11-19 7:54 ` Tino Keitel
2010-11-19 21:42 ` Chris Wilson
2010-11-23 21:47 ` Tino Keitel
2010-11-23 22:42 ` [PATCH] drm/i915/sdvo: Always fallback to querying the shared DDC line Chris Wilson
2010-11-23 23:02 ` Tino Keitel
2010-11-21 16:33 ` DVI/EDID broken with Intel i945 graphics and 2.6.37-rc2 Maciej Rutecki
-- strict thread matches above, loose matches on Subject: below --
2010-11-17 6:29 Tino Keitel
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='b9dded$h40vqf@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tino.keitel@tikei.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.