From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108570] AMDGPU DC not working on PCI Express 2.0?
Date: Fri, 26 Oct 2018 17:06:17 +0000 [thread overview]
Message-ID: <bug-108570-502-Qgqvq1IFhL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108570-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108570
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |NOTABUG
--- Comment #4 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to TestMode11 from comment #0)
> On RX560 I get the following in dmesg
>
> [ 8.426625] kfd kfd: skipped device 1002:67ef, PCI rejects atomics
That message is from kfd. It's for ROCm. Unrelated to DC
>
> Then in Weston start log I do not see "DRM supports atomic modesetting".
>
> Does this mean that DC is not active? Do AMDGPU DC and atomic modesetting
> only work with PCI Express 3.0?
No, DC has nothing to do with pci atomics. DC is enabled:
[ 8.690697] [drm] Display Core initialized with v3.2.02!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2657 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
prev parent reply other threads:[~2018-10-26 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 16:15 [Bug 108570] AMDGPU DC Not workin on PCI Express 2.0? bugzilla-daemon
2018-10-26 16:19 ` [Bug 108570] AMDGPU DC not working " bugzilla-daemon
2018-10-26 16:22 ` bugzilla-daemon
2018-10-26 16:43 ` bugzilla-daemon
2018-10-26 16:44 ` bugzilla-daemon
2018-10-26 17:06 ` bugzilla-daemon [this message]
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-108570-502-Qgqvq1IFhL@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).