mirror of
https://gitlab.freedesktop.org/emersion/libliftoff.git
synced 2024-12-25 21:59:11 +01:00
Document why the primary plane is a special case
For instance, i915 requires the primary plane to be enabled.
This commit is contained in:
parent
8a971695bd
commit
447a9e8921
1 changed files with 4 additions and 2 deletions
6
alloc.c
6
alloc.c
|
@ -52,8 +52,10 @@
|
|||
*
|
||||
* 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
|
||||
* composited. The primary plane is the first that will be allocated. Then all
|
||||
* other planes will be allocated, from the topmost one to the bottommost one.
|
||||
* composited. The primary plane is the first that will be allocated, because
|
||||
* 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
|
||||
* as a special case. If it's set on layers, it adds additional constraints on
|
||||
|
|
Loading…
Reference in a new issue