Find a file
Simon Ser 42db49c6fe
Guess zpos from plane type
Many drivers don't expose the zpos plane property. We can guess it from the
plane type though: primary, overlay, cursor. Except some drivers expose
underlays too: underlays, primary, overlay, cursor. Underlay planes don't have a
special type, they are just marked as overlays. To detect them, check whether
their plane ID is less than the primary plane ID.

References: https://github.com/emersion/libhwc/issues/3
2019-09-08 18:33:09 +03:00
include Guess zpos from plane type 2019-09-08 18:33:09 +03:00
.editorconfig Initial experiments 2019-08-21 23:07:37 +03:00
.gitignore Initial experiments 2019-08-21 23:07:37 +03:00
display.c Guess zpos from plane type 2019-09-08 18:33:09 +03:00
example.c Basic brute-force plane allocation 2019-09-08 16:32:38 +03:00
layer.c Initial experiments 2019-08-21 23:07:37 +03:00
LICENSE Add LICENSE 2019-08-21 23:13:35 +03:00
list.c Initial experiments 2019-08-21 23:07:37 +03:00
meson.build Initial experiments 2019-08-21 23:07:37 +03:00
output.c Check plane is compatible with CRTC 2019-09-08 17:41:25 +03:00
README.md Add README 2019-08-21 23:12:11 +03:00

libhwc

Lightweight hardware composer library for libdrm.

libhwc eases the use of KMS planes from userspace without standing in your way. Users create "virtual planes" called layers, set KMS properties on them, and libhwc will allocate planes for these layers if possible.

Building

Depends on libdrm. Requires universal planes and atomic.

meson build/
ninja -C build/

License

MIT