commit | af1fd2f1173b16af43d8f630975b1beeaf641f86 | [log] [tgz] |
---|---|---|
author | Laurent Pinchart <laurent.pinchart@ideasonboard.com> | Wed Jun 20 05:56:11 2018 +0300 |
committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | Wed Jun 20 13:14:22 2018 +0300 |
tree | 0b830a1156a836e151f8d296696591869f119d7a | |
parent | 33246d9b5fb0347aabd62caac1da03440f9e1634 [diff] |
py: sync: Fix event handling Fancy event handling was dropped in commit 95de32aa7fbb ("py: drop the fancy event handling"). Python tests were updated, but one commit call got forgotten in the sync.py test. Fix it. Fixes: 95de32aa7fbb ("py: drop the fancy event handling") Reported-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> 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