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: Sun, 30 Nov 2014 13:03:30 +0000 [thread overview]
Message-ID: <bug-86861-502-qSgunR2BJ6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86861-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 901 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86861
--- Comment #1 from Christian König <deathsimple@vodafone.de> ---
Sounds like just another buggy KVM switch to me.
The basic problem is that the I²C used to read the EDID assumes that you only
have two endpoints on the wire - the display and the gfx hardware. So properly
designed KVM switches have an micro-controller which fetches the EDID from the
monitor on connect and forwards the EDID to each connected system if requested.
Otherwise you run into problems when by pure coincident two systems try to
fetch the EDID at the same time.
Without the EDID the gfx hardware has no idea what resolutions the display can
handle and most likely doesn't choose the optimal one. Easiest workaround is
manually set the necessary resolution for the display.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1806 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
next prev parent reply other threads:[~2014-11-30 13:03 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 [this message]
2014-11-30 19:21 ` bugzilla-daemon
2014-12-01 2:34 ` 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-86861-502-qSgunR2BJ6@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).