All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102931] Radeon : EDID Reading Incorrectly
Date: Mon, 17 Aug 2015 02:02:31 +0000	[thread overview]
Message-ID: <bug-102931-2300-riIxMqwTKZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-102931-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=102931

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com

--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
IIRC, get-edid doesn't actually probe any i2c buses, it uses vm86 to do vbe
calls to the vbios.  vbe will only provide the edid for whatever monitor it
happened to probe at boot and likely won't work correctly once a real driver is
loaded.  It's also not multi-head aware so if you have multiple monitors
attached or are using a different display than what was available at boot it
probably won't work.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-08-17  2:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15 13:08 [Bug 102931] New: Radeon : EDID Reading Incorrectly bugzilla-daemon
2015-08-17  2:02 ` bugzilla-daemon [this message]
2015-08-17  2:03 ` [Bug 102931] " bugzilla-daemon
2015-08-17  7:19 ` bugzilla-daemon
2015-08-17  9:16 ` bugzilla-daemon
2015-08-17  9: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-102931-2300-riIxMqwTKZ@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 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.