From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86861] [rv6xx] When using a hardware KVM switch between computers EDID sometimes not detected/display goes fuzzy
Date: Mon, 01 Dec 2014 02:34:25 +0000 [thread overview]
Message-ID: <bug-86861-502-Ix0vCaxb4Z@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86861-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1057 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86861
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTOURBUG
--- Comment #3 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Shawn Starr from comment #2)
> The newer firmware updates don't address VGA EDID detection, at least the
> documentation doesn't list this.
>
> One thought though, we don't cache the EDID information if it was previously
> detected? If you switch the screen, does that effectively mean the cable is
> disconnected on the other computer?
For analog displays like VGA, the drm core polls every 10 seconds or so to see
if the monitor is still there since the older analog connctors like VGA do not
support hotplug like digital connectors like DVI or HDMI do.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2789 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2014-12-01 2:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 21:31 [Bug 86861] [rv6xx] When using a hardware KVM switch between computers EDID sometimes not detected/display goes fuzzy bugzilla-daemon
2014-11-30 13:03 ` bugzilla-daemon
2014-11-30 19:21 ` bugzilla-daemon
2014-12-01 2:34 ` bugzilla-daemon [this message]
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-86861-502-Ix0vCaxb4Z@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