dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97590] Fury X (Fiji) LEDs do not reflect GPU load
Date: Sun, 04 Sep 2016 19:23:44 +0000	[thread overview]
Message-ID: <bug-97590-502-aqbtGvS07Q@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97590-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from John Bridgman <john.bridgman@amd.com> ---
There was a Phoronix article recently celebrating the addition of an LED driver
to the Nouveau driver... guessing that something similar will need to be done
for amdgpu eventually.

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

[-- Attachment #1.2: Type: text/html, Size: 1149 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-09-04 19:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04  8:55 [Bug 97590] Fury X (Fiji) LEDs do not reflect GPU load bugzilla-daemon
2016-09-04 19:23 ` bugzilla-daemon [this message]
2016-09-05  9:44 ` bugzilla-daemon
2017-02-22 13:03 ` bugzilla-daemon
2017-02-22 16:23 ` bugzilla-daemon
2017-02-22 22:25 ` bugzilla-daemon
2017-02-22 23:36 ` bugzilla-daemon
2017-02-23 13:16 ` bugzilla-daemon
2017-02-23 13:46 ` bugzilla-daemon
2017-02-23 14:18 ` bugzilla-daemon
2017-02-23 15:32 ` bugzilla-daemon
2017-02-23 15:41 ` bugzilla-daemon
2017-02-23 21:12 ` bugzilla-daemon
2017-02-23 21:21 ` bugzilla-daemon
2017-02-25 11:56 ` bugzilla-daemon
2017-02-28 15:12 ` bugzilla-daemon
2017-05-21  3:33 ` bugzilla-daemon
2017-05-22  1:19 ` 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-97590-502-aqbtGvS07Q@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).