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 15:10:30 +0000 [thread overview]
Message-ID: <bug-49789-502-PNO9ZMyunv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-49789-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=49789
--- Comment #3 from Harald Judt <h.judt@gmx.at> 2012-05-11 08:10:30 PDT ---
Can I somehow find out (log files, whatever), whether the monitor has an EDID
or not, after it has been connected? Because then I could turn off the polling
for the time being, or at least reduce the polling interval.
With regard to the events: I've tried using udev to react to the hotplug
events, but it wouldn't work reliably. It would successfully recognize a
monitor the first time, but fail to trigger on disconnect or later connect
attempts. So unfortunately, my approach was and probably is the only
viable/reliable here to do it automatically.
--
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 15:10 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
2012-05-11 15:10 ` bugzilla-daemon [this message]
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-PNO9ZMyunv@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).