tag | 167deb6b626d28267757ff3f0f283d0af88acaa5 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Mon Aug 15 09:52:02 2022 -0700 |
object | 99faaa619d681993e01cef564693d5d5880c05dd |
Android 13.0.0 Release 3 (TP1A.220624.021.A1)
commit | 99faaa619d681993e01cef564693d5d5880c05dd | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Sep 19 01:03:35 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Sep 19 01:03:35 2021 +0000 |
tree | 2a349626debe337534905374d428e93e594fb813 | |
parent | 8c6940f1384d5f7d2bc07619b65fd493884b1db6 [diff] | |
parent | f0687c8a10b3e371dbe09214db6664e37c283cca [diff] |
Snap for 7745935 from f0687c8a10b3e371dbe09214db6664e37c283cca to tm-release Change-Id: Icdc1901d8c8fa65c6271d0df2714a80f66812e1f
kms++ is a C++17 library for kernel mode setting.
Also included are some simple utilities for KMS and python bindings for kms++.
To build the Python bindings you need to set up the git-submodule for pybind11:
git submodule update --init
And to compile:
meson build ninja -C build
meson build --cross-file=<path-to-meson-cross-file> ninja -C build
Here is my cross file for arm32 (where ${BROOT} is path to my buildroot output dir):
[binaries] c = ['ccache', '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-gcc'] cpp = ['ccache', '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-g++'] ar = '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-ar' strip = '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-strip' pkgconfig = '${BROOT}/host/bin/pkg-config' [host_machine] system = 'linux' cpu_family = 'arm' cpu = 'arm' endian = 'little'
You can use meson options to configure the build. E.g.
meson build -Dbuildtype=debug -Dkmscube=true
Use meson configure build
to see all the configuration options and their current values.
kms++ specific build options are:
Option name | Values | Default | Notes |
---|---|---|---|
pykms | true, false | true | Python bindings |
kmscube | true, false | false | GLES kmscube |
omap | enabled, disabled, auto | auto | libdrm-omap support |
You can use the following runtime environmental variables to control the behavior of kms++.
Variable | Description |
---|---|
KMSXX_DISABLE_UNIVERSAL_PLANES | Set to disable the use of universal planes |
KMSXX_DISABLE_ATOMIC | Set to disable the use of atomic modesetting |
KMSXX_DEVICE | Path to the card device node to use |
KMSXX_DRIVER | Name of the driver to use. The format is either “drvname” or “drvname:idx” |
You can run the python code directly from the build dir by defining PYTHONPATH env variable. For example:
PYTHONPATH=build/py py/tests/hpd.py