[Bug 101387] amdgpu display corruption and hang on AMD A10-9620P

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jun 21 06:26:10 UTC 2017


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

--- Comment #22 from Carlo Caione <carlo at caione.org> ---
> Plymouth shouldn't get the values with drmModeCrtcGetGamma — there's no
> guarantee that the CLUT contains suitable values at that point (e.g. the
> hardware could currently be programmed for a different colour bit depth
> in the first place).
Ok, but at this point I wonder (sorry, not really familiar with libdrm) why the
value reported by drmModeCrtcGetGamma are not coherent with the values
currently programmed in hardware. Is this a common thing?

If __immediately__ before drmModeSetCrtc I do drmModeCrtcGetGamma +
drmModeCrtcSetGamma with the values retrieved, everything works fine with the
correct colors, so the CLUTs returned by drmModeCrtcGetGamma actually contain
suitable / correct values but apparently these are different from what is
programmed in the hardware.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170621/1ba1035b/attachment.html>


More information about the dri-devel mailing list