dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107390] [BISECTED] EDID read failure breaks display mirroring
Date: Fri, 27 Jul 2018 12:11:37 +0000	[thread overview]
Message-ID: <bug-107390-502-604mJll5KW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107390-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107390

--- Comment #6 from Justinas Narusevicius <junaru@gmail.com> ---
Hey Alex,

Yes ac916c914c3156e53505e9ea3a9d1495518bf873 was found by bisecting mainline
kernel between tags of v4.16 (0adb32858b0bddf4ada5f364a84ed60b196dbcda good)
and v4.17-rc1 (60cc43fc888428bb2f18f08997432d426a243338 bad)

I can confirm that reverting ac916c914c3156e53505e9ea3a9d1495518bf873 via the
attached patch on current mainline kernel HEAD
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd3f77d74ac31b4627cdfa70812338076a1ea475)
fixes all three issues.

* Mirroring is available once again.
* Extended desktop mode can now use all the resolutions up to and including 4K.
* There's no 3rd erroneous display on HDMI-A-2 anymore.

Should i test this against
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next or any
other specific branch?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2030 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-07-27 12:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 18:10 [Bug 107390] [BISECTED] EDID read failure breaks display mirroring bugzilla-daemon
2018-07-26 18:12 ` bugzilla-daemon
2018-07-26 18:13 ` bugzilla-daemon
2018-07-26 18:15 ` bugzilla-daemon
2018-07-26 18:16 ` bugzilla-daemon
2018-07-26 18:16 ` bugzilla-daemon
2018-07-26 18:17 ` bugzilla-daemon
2018-07-26 20:55 ` bugzilla-daemon
2018-07-26 20:56 ` bugzilla-daemon
2018-07-27 12:11 ` bugzilla-daemon [this message]
2018-07-27 12:12 ` bugzilla-daemon
2018-07-27 14:33 ` bugzilla-daemon
2018-07-31 19:33 ` bugzilla-daemon
2018-07-31 21:16 ` bugzilla-daemon
2018-07-31 21:23 ` bugzilla-daemon
2018-08-01 11:59 ` bugzilla-daemon
2018-08-01 11:59 ` bugzilla-daemon
2018-08-01 12:49 ` bugzilla-daemon
2018-08-01 13:55 ` bugzilla-daemon
2018-08-01 14:10 ` bugzilla-daemon
2018-08-01 14:51 ` bugzilla-daemon
2018-08-01 14:53 ` bugzilla-daemon
2018-08-01 15:34 ` bugzilla-daemon
2019-11-19  8:45 ` 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-107390-502-604mJll5KW@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