Comment=
# 9
on bug 97590<=
/a>
from Adam Bolte
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 =
[details] [review] applies cleanly to 4.10 so I ended u=
p using that. I
tried to test attachment 129851 [detai=
ls] [review] 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) b=
ut
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 sa=
me
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 curre=
ntly
able, and the LEDs are actually doing the right thing. No big deal either w=
ay.
Thanks again Alex.