[AMD Official Use Only - Approved for External Use] Hi Simon, Yes, I did have a chance to wrap this up, indeed :-) It turned out this and other similar setup was hitting a legit HW limitation. I added a patch (please see attached) that'd fail this config at validation time. The patch has been merged for upstreaming at the beginning of February time-frame, not sure if it made it to the public repo by now. Please let me know if you need more info on this. Regards, Nikola -----Original Message----- From: Simon Ser <contact@xxxxxxxxxxx> Sent: Friday, February 19, 2021 4:22 PM To: Cornij, Nikola <Nikola.Cornij@xxxxxxx> Cc: Alex Deucher <alexdeucher@xxxxxxxxx>; Kazlauskas, Nicholas <Nicholas.Kazlauskas@xxxxxxx>; Deucher, Alexander <Alexander.Deucher@xxxxxxx>; Wentland, Harry <Harry.Wentland@xxxxxxx>; amd-gfx list <amd-gfx@xxxxxxxxxxxxxxxxxxxxx> Subject: RE: Overlay issues Hi, On Wednesday, December 23rd, 2020 at 6:48 AM, Cornij, Nikola <Nikola.Cornij@xxxxxxx> wrote: > Another interim update: so far to me it looks like this is an issue if > there's fewer than 24 pixels left on the screen when moving the FB > outside of the left edge (e.g. with 300x300 FB size, it repros with X > = -280). When this happens, what looks like a boundary condition in > our driver is hit and destination rectangle update is skipped. > > I need to do some more digging to fully understand why is this > condition in place and how to avoid it. Did you have the chance to continue working on this? Thanks, Simon
Attachment:
0001-drm-amd-display-Reject-too-small-viewport-size-when-.patch
Description: 0001-drm-amd-display-Reject-too-small-viewport-size-when-.patch
_______________________________________________ amd-gfx mailing list amd-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/amd-gfx
