commit | db0da1f33c7d688e84e9cd7ff0551842bb68ca6f | [log] [tgz] |
---|---|---|
author | Tomi Valkeinen <tomi.valkeinen@ti.com> | Thu Jan 17 17:24:25 2019 +0200 |
committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | Thu Jan 17 17:43:48 2019 +0200 |
tree | 58abaa24d29b2c592b9de03e1d4c1aaa23e22806 | |
parent | d49777b00e844ac77e0f3b0cfb9b9e07257b4c26 [diff] |
card: another try with card constructors Let's try again with the card constructors. Card::open_modesetting_card() is removed. The main constructor is Card(const std::string& dev_path = ""). If dev_path is set, the device node with that path is used. If dev_path is not set, the behavior is similar as previously, except a modeset capable card is used at the third step: - If KMSXX_DEVICE env variable is set, the card device with that path is opened. - If KMSXX_DRIVER env variable is set, the card with the given driver name and index is opened. The format is either "drvname" or "drvname:idx". - If neither env variable is given, the first modeset capable card is opened. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
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_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 |
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