https://bugs.kde.org/show_bug.cgi?id=511274
--- Comment #16 from [email protected] --- > I'm pretty sure this is a kernel bug - KWin uses a format with alpha, > and the driver just ignores the alpha channel. That is quite possible indeed. I did some more tests and these are the findings: - I could not reproduce it on a Rock64 (rk3328) - I could not reproduce it on a Quartz64-B (rk3566, same as PineTab2) - 'my' rockchip-drm expert could not reproduce it on his rk3566-box-demo - ``cat /sys/kernel/debug/dri/0/vop2/summary`` gave some interesting results: rk3566-box-demo: Video Port0: ACTIVE Connector: HDMI-A-1 ... Display mode: 1920x1080p60 ... Smart0-win0: ACTIVE ... src: pos[0, 0] rect[1920 x 1080] dst: pos[0, 0] rect[1920 x 1080] ... Esmart0-win0: ACTIVE ... src: pos[0, 0] rect[32 x 32] dst: pos[1702, 615] rect[32 x 32] ... Quartz64-B: Video Port0: ACTIVE Connector: HDMI-A-1 ... Display mode: 1920x1080p60 ... Smart0-win0: ACTIVE ... src: pos[0, 0] rect[1920 x 1080] dst: pos[0, 0] rect[1920 x 1080] Esmart0-win0: ACTIVE ... src: pos[0, 0] rect[32 x 32] dst: pos[497, 402] rect[32 x 32] ... PineTab2: Video Port0: DISABLED Video Port1: ACTIVE Connector: DSI-1 ... Display mode: 800x1280p60 ... Esmart0-win0: ACTIVE ... src: pos[0, 0] rect[800 x 1280] dst: pos[0, 0] rect[800 x 1280] ... Cluster0-win0: ACTIVE ... src: pos[0, 0] rect[32 x 32] dst: pos[290, 875] rect[32 x 32] ... *I*IUC different 'planes' are used on the PineTab then in the other cases. My rockchip-drm expert also said this: > I suspect the root cause of this issue might be that the VOP driver > didn't handle the alpha blending of AFBC format properly when > Cluster0-win0 was used as cursor plane. -- You are receiving this mail because: You are watching all bug changes.
