From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not usable) with RX580, amdgpu, dc=1 (of course), regression - [bisected]
Date: Fri, 26 Oct 2018 20:20:37 +0000 [thread overview]
Message-ID: <bug-108096-502-x4x0lb1Sua@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108096-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 351 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108096
--- Comment #16 from Andrey Grodzovsky <andrey.grodzovsky@amd.com> ---
Question is do you have " winsys/amdgpu: pass the BO list via the CS ioctl on
DRM >= 3.27.0" commit in your MESA tree ? I am not clear on that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1301 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:[~2018-10-26 20:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 3:38 [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not useable) with RX580, amdgpu, dc=1 (of course), regression bugzilla-daemon
2018-09-29 3:40 ` bugzilla-daemon
2018-09-29 3:43 ` bugzilla-daemon
2018-09-29 3:43 ` bugzilla-daemon
2018-09-29 3:44 ` bugzilla-daemon
2018-09-29 3:45 ` bugzilla-daemon
2018-09-29 3:47 ` bugzilla-daemon
2018-09-29 3:48 ` bugzilla-daemon
2018-09-30 13:33 ` bugzilla-daemon
2018-10-23 23:31 ` bugzilla-daemon
2018-10-23 23:41 ` [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not usable) " bugzilla-daemon
2018-10-24 8:33 ` bugzilla-daemon
2018-10-24 9:01 ` bugzilla-daemon
2018-10-25 0:56 ` bugzilla-daemon
2018-10-25 1:24 ` bugzilla-daemon
2018-10-26 3:36 ` [Bug 108096] [amd-staging-drm-next] SDDM screen corruption (not usable) with RX580, amdgpu, dc=1 (of course), regression - [bisected] bugzilla-daemon
2018-10-26 8:06 ` bugzilla-daemon
2018-10-26 12:05 ` bugzilla-daemon
2018-10-26 20:20 ` bugzilla-daemon [this message]
2018-10-26 23:29 ` bugzilla-daemon
2018-10-29 11:08 ` bugzilla-daemon
2018-10-29 14:08 ` bugzilla-daemon
2018-10-29 14:56 ` bugzilla-daemon
2018-10-29 17:08 ` bugzilla-daemon
2018-10-30 20:01 ` bugzilla-daemon
2018-11-01 1:42 ` bugzilla-daemon
2018-11-01 1:44 ` bugzilla-daemon
2018-11-01 1:44 ` bugzilla-daemon
2018-11-01 14:32 ` bugzilla-daemon
2018-11-07 22:11 ` bugzilla-daemon
2018-11-07 22:13 ` 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-108096-502-x4x0lb1Sua@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;
as well as URLs for NNTP newsgroup(s).