From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49789] External monitor flickers on xrandr or cat /sys/class/drm/card0-VGA-1/status
Date: Fri, 11 May 2012 14:50:48 +0000 [thread overview]
Message-ID: <bug-49789-502-m4WZTMyLc5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-49789-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=49789
Alex Deucher <agd5f@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |NOTABUG
--- Comment #2 from Alex Deucher <agd5f@yahoo.com> 2012-05-11 07:50:48 PDT ---
The driver uses load detection to see if a monitor is connected if it does not
provide an EDID. The process of detecting load on the pins will cause a
momentary distortion of the image in some cases. There's not much else you can
do if you want to be able to detect the presence or lack of a monitor without
an EDID. BTW, for monitors with an EDID the driver will automatically generate
events when they are connected or disconnected so there is no need to poll.
Unfortunately, load detection is the only option for analog monitors that have
no EDID. Digital monitors will generate a hotplug interrupt.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-05-11 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 11:37 [Bug 49789] New: External monitor flickers on xrandr or cat /sys/class/drm/card0-VGA-1/status bugzilla-daemon
2012-05-11 11:38 ` [Bug 49789] " bugzilla-daemon
2012-05-11 14:50 ` bugzilla-daemon [this message]
2012-05-11 15:10 ` bugzilla-daemon
2012-05-11 17:23 ` bugzilla-daemon
2012-05-15 9:01 ` bugzilla-daemon
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=bug-49789-502-m4WZTMyLc5@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).