Miroirs/libliftoff
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/emersion/libliftoff.git synced 2024-12-27 21:59:24 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Document why the primary plane is a special case

Browse source 
For instance, i915 requires the primary plane to be enabled.
This commit is contained in:
Simon Ser 2021-08-13 12:38:05 +02:00
parent 8a971695bd
commit 447a9e8921
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
alloc.c
View file

@ -52,8 +52,10 @@
* *
* In practice, the primary plane is treated separately. This is where layers * In practice, the primary plane is treated separately. This is where layers
* that can't be mapped to any plane (e.g. layer 1 in our example) will be * that can't be mapped to any plane (e.g. layer 1 in our example) will be
* composited. The primary plane is the first that will be allocated. Then all * composited. The primary plane is the first that will be allocated, because
* other planes will be allocated, from the topmost one to the bottommost one. * some drivers require it to be enabled in order to light up any other plane.
* Then all other planes will be allocated, from the topmost one to the
* bottommost one.
* *
* The "zpos" property (which defines ordering between layers/planes) is handled * The "zpos" property (which defines ordering between layers/planes) is handled
* as a special case. If it's set on layers, it adds additional constraints on * as a special case. If it's set on layers, it adds additional constraints on