-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual DRM plane artifacts on vertical edges. #6264
Comments
Might be best to provide minimal test code that shows the issue(*). (*) it may be possible to configure kmstest in a similar way |
(Sorry, read and then forgot about this issue). Can you also provide the contents of /sys/kernel/debug/dri/1/hvs_dlists, so that we can analyse what the HVS has been asked to compose? |
Not sure. I've not observed it with just a single display so far, but that might just be a coincidence. The dual display layout was just something I randomly put together and other layouts even across both displays don't show this glitch.
|
I won't be able to provide a condensed test case within the next two weeks, but I can try to put one together after that. Don't put too much energy into this in the mean time. |
Ok. Got something to easily reproduce this:
The issue also happens with 64bit. If you want to run that instead, download the 64bit binary of info-beamer from here and replace the included Let me know if that's helpful or if there's anything else I might provide.
|
Describe the bug
While playing around in my software, I managed to come across a DRM plane layout that results in artifacts on vertical plane edges. Look at this screenshot:
I'm playing three videos across two displays (separated by the white line in the screenshot). As a result my software splits the middle video into two planes (labeled '2' and '3'). To reduce overdraw, my software also removes the non-visible part of the plane '3' that's hidden behind the plane '4'.
The video is 560x360 pixel, DRM "YU12". The relevant output in
/sys/kernel/debug/dri/1/state
for plane '3' is:For plane '4':
So plane '4' touches plane '3' at x=360. That edge has odd bleeding of pixels going on:
Steps to reproduce the behaviour
Not sure yet. That specific configuration doesn't work. Resizing the middle video (and thus plane '2' and '3') likely fixes the issue. Tested only on a Pi5 for now.
Device (s)
Raspberry Pi 5
System
My custom info-beamer OS. Using 6.6.33 kernel from https://github.com/raspberrypi/rpi-firmware:
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: