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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Comment # 20 on bug 101387 from
> That could be a plymouth bug. I've noticed that it doesn't seem to call
> drmModeCrtcSetGamma to make sure the display CLUTs are initialized to
> appropriate values.
Can you expand on this a little bit?

I have (by chance TBH) fixed plymouth basically reading the CLUTs using
drmModeCrtcGetGamma() when plymouthd starts and writing them back using
drmModeCrtcSetGamma() before drmModeSetCrtc() is called when the reboot splash
has to be displayed.

But it's not clear to me why this is needed at all since in theory I'm writing
back the same CLUTs values read by drmModeCrtcGetGamma() but at the same time
if I do not do that, I have image corruption.

Any hint about this?


You are receiving this mail because:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux