From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199085] Multiple [drm] Got external EDID base block and 0 extensions messages
Date: Wed, 11 Apr 2018 15:01:09 +0000 [thread overview]
Message-ID: <bug-199085-2300-tJxKyFyHJv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199085-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199085
--- Comment #6 from Jani Nikula (jani.nikula@intel.com) ---
The firmware EDID handling was moved at a lower level in the stack to be a more
transparent replacement for the display EDID. Without this, many features were
erroneously parsed from the display EDID, which was in conflict with the
firmware EDID.
This means that any time the driver would read the EDID, it gets loaded as the
firmware EDID.
It's arguably something that should be improved in the driver to not keep
reading the EDID so many times over, whether it's display or firmware EDID.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-11 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 9:57 [Bug 199085] New: Multiple [drm] Got external EDID base block and 0 extensions messages bugzilla-daemon
2018-03-12 10:00 ` [Bug 199085] " bugzilla-daemon
2018-03-12 13:45 ` bugzilla-daemon
2018-03-19 8:31 ` bugzilla-daemon
2018-03-19 8:55 ` bugzilla-daemon
2018-04-01 10:42 ` bugzilla-daemon
2018-04-11 15:01 ` bugzilla-daemon [this message]
2018-04-12 8:40 ` 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-199085-2300-tJxKyFyHJv@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 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).