blob: feb43d7017ca9128fc59354a510aaa85f89f73d2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
|
[](https://travis-ci.org/tomba/kmsxx)
# kms++ - C++ library for kernel mode setting
kms++ is a C++11 library for kernel mode setting.
Also included are some simple utilities for KMS and python bindings for kms++.
## Utilities
- kmstest - set modes and planes and show test pattern on crtcs/planes, and test page flips
- kmsprint - print information about DRM objects
- kmsview - view raw images
- kmscube - rotating 3D cube on crtcs/planes
- kmscapture - show captured frames from a camera on screen
## Dependencies:
- libdrm
- Python 3.x (for python bindings)
## Build instructions:
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
```
## Cross compiling instructions:
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)
```
## Build options
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
## Env variables
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"
## Python notes
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
```
|
