From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110371] HP Dreamcolor display *Error* No EDID read
Date: Thu, 02 May 2019 03:09:09 +0000 [thread overview]
Message-ID: <bug-110371-502-lXMqfw87t2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110371-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 747 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110371
--- Comment #7 from Babblebones@gmail.com ---
Created attachment 144124
--> https://bugs.freedesktop.org/attachment.cgi?id=144124&action=edit
Dmesg drm.debug=4
Funny enough it complains about missing EDID in this one too. May not even be
the issue now that I'm coming in on it.
But I seem to have found the commit where my panel breaks down.
It's a big drm-next merge. It has to be one of the core changes listed on the
changelog.
I'm not a git wizard, is there any way to get more granular about this commit?
Anyone have an idea what's broken in here?
54c88a029a0a86fe00a0ee7d2a15ee08e6d04db9
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1626 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-02 3:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 3:38 [Bug 110371] HP Dreamcolor display *Error* No EDID read bugzilla-daemon
2019-04-10 7:38 ` bugzilla-daemon
2019-04-13 2:14 ` bugzilla-daemon
2019-04-18 14:40 ` bugzilla-daemon
2019-04-18 14:59 ` bugzilla-daemon
2019-04-18 15:11 ` bugzilla-daemon
2019-04-18 15:29 ` bugzilla-daemon
2019-04-19 17:59 ` bugzilla-daemon
2019-05-02 3:09 ` bugzilla-daemon [this message]
2019-05-05 17:48 ` bugzilla-daemon
2019-05-05 18:31 ` bugzilla-daemon
2019-05-10 22:32 ` bugzilla-daemon
2019-05-15 5:02 ` bugzilla-daemon
2019-10-15 2:28 ` 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-110371-502-lXMqfw87t2@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