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 96786] AMD Display Library (ADL) functionality unavailable/not working
Date: Sat, 02 Jul 2016 19:36:20 +0000	[thread overview]
Message-ID: <bug-96786-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 96786
           Summary: AMD Display Library (ADL) functionality
                    unavailable/not working
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu-pro
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: jolan@jolan.org

Hi,

I recently upgraded from Catalyst 15.12 and functionality exposed via ADL is
not working at all; I cannot even get temperature/fan speed reporting to work.

I'm not sure if this is expected or not. Seems this could be replaced/supported
by the powerplay work in the upcoming 4.7 kernel.

AMDGPU-Pro: 16.30.3.306809
Kernel: 4.6.3-1-ARCH
Hardware: Fiji/R9 Fury X

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

[-- Attachment #1.2: Type: text/html, Size: 2268 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

             reply	other threads:[~2016-07-02 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02 19:36 bugzilla-daemon [this message]
2016-07-05 16:44 ` [Bug 96786] AMD Display Library (ADL) functionality unavailable/not working 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-96786-502@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