From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104275] Stoney Ridge laptop display goes blank after HDMI gets plugged/unplugged in extended mode.
Date: Wed, 20 Dec 2017 09:58:14 +0000 [thread overview]
Message-ID: <bug-104275-502-aOm13UnUAj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104275-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 704 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104275
--- Comment #8 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Alex_Zhang1 from comment #7)
Without the patch referenced in comment 3, a buffer must be pinned to VRAM
before it can be scanned out (displayed). The problem described in this report
happens because pinning to VRAM fails, because there isn't enough space in
VRAM. The patch allows buffers to be pinned to GTT instead of VRAM for scanout.
Another DC patch is probably needed to fix the garbled display described in
comment 4. Maybe try the patch on top of the amd-staging-drm-next branch.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1690 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
next prev parent reply other threads:[~2017-12-20 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 3:51 [Bug 104275] Stoney Ridge laptop display goes blank after HDMI gets plugged/unplugged in extended mode bugzilla-daemon
2017-12-15 3:52 ` bugzilla-daemon
2017-12-15 3:52 ` bugzilla-daemon
2017-12-15 9:25 ` bugzilla-daemon
2017-12-15 9:57 ` bugzilla-daemon
2017-12-15 9:59 ` bugzilla-daemon
2017-12-15 10:30 ` bugzilla-daemon
2017-12-20 5:56 ` bugzilla-daemon
2017-12-20 9:58 ` bugzilla-daemon [this message]
2017-12-20 14:31 ` bugzilla-daemon
2017-12-25 6:38 ` bugzilla-daemon
2017-12-25 8:35 ` bugzilla-daemon
2018-01-02 9:53 ` bugzilla-daemon
2018-01-02 16:07 ` bugzilla-daemon
2018-12-20 7:18 ` 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-104275-502-aOm13UnUAj@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