commit | 1a651be7a46073b1095a492d497bd089e9242087 | [log] [tgz] |
---|---|---|
author | Matt Hoosier <matt.hoosier@garmin.com> | Tue May 12 14:49:40 2020 -0500 |
committer | Matt Hoosier <matt.hoosier@garmin.com> | Fri May 15 08:07:26 2020 -0500 |
tree | 97e5323de13622552b0048f3073bc2782408d8c8 | |
parent | 4091a630137400dfac389215a7ec8c43b191ec5f [diff] |
resmgr: add release() methods This makes the ResourceManager class much more functional for uses where the set of resources used to scan out a scene changes from frame to frame. The atomic modesetting API discipline requires a brute-force search to find a compatible pairing of planes/etc, and being able to reserve bits incrementally is much simpler than throwing out the entire resourcemanager and make a new one each time a resource reserved in a tentative attempt to probe its compatibility with an test-mode atomic commit, turns out not to pan out.
kms++ is a C++11 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:
$ mkdir build $ cd build $ cmake .. $ make -j4
Directions for cross compiling depend on your environment.
These are for mine with buildroot:
$ mkdir build $ cd build $ cmake -DCMAKE_TOOLCHAIN_FILE=<buildrootpath>/output/host/usr/share/buildroot/toolchainfile.cmake .. $ make -j4
Your environment may provide similar toolchainfile. If not, you can create a toolchainfile of your own, something along these lines:
SET(CMAKE_SYSTEM_NAME Linux) SET(BROOT "<buildroot>/output/") # specify the cross compiler SET(CMAKE_C_COMPILER ${BROOT}/host/usr/bin/arm-buildroot-linux-gnueabihf-gcc) SET(CMAKE_CXX_COMPILER ${BROOT}/host/usr/bin/arm-buildroot-linux-gnueabihf-g++) # where is the target environment SET(CMAKE_FIND_ROOT_PATH ${BROOT}/target ${BROOT}/host) SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY) SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
You can use the following cmake flags to control the build. Use -DFLAG=VALUE
to set them.
Option name | Values | Default | Notes |
---|---|---|---|
CMAKE_BUILD_TYPE | Release/Debug | Release | |
BUILD_SHARED_LIBS | ON/OFF | OFF | |
KMSXX_ENABLE_PYTHON | ON/OFF | ON | |
KMSXX_ENABLE_KMSCUBE | ON/OFF | OFF | |
KMSXX_ENABLE_LIBDRMOMAP | ON/OFF | OFF | |
KMSXX_PYTHON_VERSION | python3/python2 | python3;python2 | Name of the python pkgconfig file |
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