[PATCH v2 0/5] amd/display: improve atomic cursor checks

Simon Ser contact at emersion.fr
Wed Mar 17 08:21:46 UTC 2021


On Thursday, March 11th, 2021 at 3:13 PM, Michel Dänzer <michel at daenzer.net> wrote:

> > I'm not a fan of adding kernel hacks like setting up a transparent FB, when
> > user-space can just avoid the failure with atomic test-only commits (and e.g.
> > use the overlay to display the cursor image instead of the cursor plane).
>
> I'm not a fan of requiring each atomic client to handle this complexity.

That's just how atomic works though. User-space is expected to incrementally
build the atomic request, bailing out if something doesn't work along the way.
Doing it the old way (ie. issuing singular atomic commits, ie. using the atomic
API just like the legacy API is used) won't work in many situations anyways.

Plus, a library such as libliftoff will just handle all of that complexity for
you.


More information about the amd-gfx mailing list