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 97590] Fury X (Fiji) LEDs do not reflect GPU load
Date: Thu, 23 Feb 2017 14:18:57 +0000	[thread overview]
Message-ID: <bug-97590-502-NRYvSzGeOM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97590-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Adam Bolte <abolte@systemsaviour.com> ---
I'm very excited to say that this patch is working great. Huge thanks! I know
it's crazy but there's something very satisfying about having the LEDs show
what the cards are doing. :)

I noticed attachment 129828 applies cleanly to 4.10 so I ended up using that. I
tried to test attachment 129851 but wasn't sure which repo/branch I was
supposed to apply it to. I tried
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (master
branch) and git://people.freedesktop.org/~airlied/linux (drm-next branch) but
I'm clearly looking in the wrong place. Happy to re-test if you point me in the
right direction of the correct kernel source code to use.

Many games were tested (including a number under Wine with Gallium on Nine and
d3d9 patches). I only tested this against the free software stack so far. I
tested the Talos Principle (to test Vulkan), a bunch of Feral ports, etc. At
all times the first Fury X LEDs on the primary card would flicker in the same
way as they do under Windows, which is terrific.

The only difference between this patch and the Windows behaviour is with the
second card at idle - Windows will display only a single green LED which I
believe indicates the card is in its lowest power mode. I was unable to
reproduce that same status with your patch. However I'm guessing this means
Windows puts the unused card in to a lower power state than AMDGPU is currently
able, and the LEDs are actually doing the right thing. No big deal either way.

Thanks again Alex.

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

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

  parent reply	other threads:[~2017-02-23 14:18 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
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 [this message]
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-NRYvSzGeOM@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