From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110371] HP Dreamcolor display *Error* No EDID read
Date: Fri, 10 May 2019 22:32:13 +0000 [thread overview]
Message-ID: <bug-110371-502-iCxZ8RG9Vk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110371-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1188 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110371
--- Comment #10 from Babblebones@gmail.com ---
Best I can tell, and I may be wrong, the error checking code was moved from the
DC part straight into DRM which now replicates the exact bug which was reverted
by the above DC commits but were never implemented for DRM.
https://www.st.com/en/touch-and-display-controllers/stdp8028.html
My dreamcolor display uses a STDP8028 chip, istting inbetween the display and
the motherboard just behind the screen, to convert a displayport signal coming
off the board into a dual channel LVDS to run the display.
https://www.st.com/en/touch-and-display-controllers/stdp8028.html
The EDID can't be read through this for some reason and it doesn't print any
modelines at all for the display so it picks the lowest resolution possible and
all the timings are incorrect resulting in the display scramble.
I hope the behavior highlighted in the above commit can help someone search for
the regression in the new DRM mode setting as it produces the exact same type
of scramble and lack of modelines.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2102 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-10 22:32 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
2019-05-05 17:48 ` bugzilla-daemon
2019-05-05 18:31 ` bugzilla-daemon
2019-05-10 22:32 ` bugzilla-daemon [this message]
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-iCxZ8RG9Vk@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 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.