a2dbfd6442
Add support for drawing the SMPTE pattern in buffers using a color-indexed frame buffer formats with two, four, or sixteen colors. Note that this still uses 256 as the CLUT size, as DRM_IOCTL_MODE_SETGAMMA enforces that the size matches against the (fixed) gamma size, while the CLUT size depends on the format. Move clearing the color LUT entries from util_smpte_index_gamma() to its caller, as only the caller knows how many entries there really are (currently DRM always assumes 256 entries). Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Acked-by: Sam Ravnborg <sam@ravnborg.org> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> --- v5: - Add Reviewed-by, v4: - Add missing C[12] to oneline-summary, - Do not remove memset() of full lut, else some entries may stay uninitialized, v3: - Add Acked-by, v2: - Split off changes to tests/modetest/modetest.c, - Add C1 and C2 support. The linuxdoc comments say userspace can query the gamma size: * drm_mode_gamma_set_ioctl - set the gamma table * * Set the gamma table of a CRTC to the one passed in by the user. Userspace can * inquire the required gamma table size through drm_mode_gamma_get_ioctl. * drm_mode_gamma_get_ioctl - get the gamma table * * Copy the current gamma table into the storage provided. This also provides * the gamma table size the driver expects, which can be used to size the * allocated storage. but the code doesn't seem to support that in an easy way (like setting red/green/blue to NULL on input, retrieving gamma_size on output), only by providing big enough buffers for red/green/blue, and looping over gamma_size until -EINVAL is no longer returned. |
||
---|---|---|
amdgpu | ||
android | ||
data | ||
etnaviv | ||
exynos | ||
freedreno | ||
include/drm | ||
intel | ||
man | ||
nouveau | ||
omap | ||
radeon | ||
tegra | ||
tests | ||
vc4 | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
Android.common.mk | ||
Android.mk | ||
CONTRIBUTING.rst | ||
CleanSpec.mk | ||
Makefile.sources | ||
README.rst | ||
RELEASING | ||
core-symbols.txt | ||
gen_table_fourcc.py | ||
libdrm.pc.in | ||
libdrm_lists.h | ||
libdrm_macros.h | ||
libsync.h | ||
meson.build | ||
meson_options.txt | ||
symbols-check.py | ||
util_double_list.h | ||
util_math.h | ||
xf86atomic.h | ||
xf86drm.c | ||
xf86drm.h | ||
xf86drmHash.c | ||
xf86drmHash.h | ||
xf86drmMode.c | ||
xf86drmMode.h | ||
xf86drmRandom.c | ||
xf86drmRandom.h | ||
xf86drmSL.c |
README.rst
libdrm - userspace library for drm ---------------------------------- This is libdrm, a userspace library for accessing the DRM, direct rendering manager, on Linux, BSD and other operating systems that support the ioctl interface. The library provides wrapper functions for the ioctls to avoid exposing the kernel interface directly, and for chipsets with drm memory manager, support for tracking relocations and buffers. New functionality in the kernel DRM drivers typically requires a new libdrm, but a new libdrm will always work with an older kernel. libdrm is a low-level library, typically used by graphics drivers such as the Mesa drivers, the X drivers, libva and similar projects. Syncing with the Linux kernel headers ------------------------------------- The library should be regularly updated to match the recent changes in the `include/uapi/drm/`. libdrm maintains a human-readable version for the token format modifier, with the simpler ones being extracted automatically from `drm_fourcc.h` header file with the help of a python script. This might not always possible, as some of the vendors require decoding/extracting them programmatically. For that reason one can enhance the current vendor functions to include/provide the newly added token formats, or, in case there's no such decoding function, to add one that performs the tasks of extracting them. For simpler format modifier tokens there's a script (gen_table_fourcc.py) that creates a static table, by going over `drm_fourcc.h` header file. The script could be further modified if it can't handle new (simpler) token format modifiers instead of the generated static table. Compiling --------- To set up meson: meson builddir/ By default this will install into /usr/local, you can change your prefix with --prefix=/usr (or `meson configure builddir/ -Dprefix=/usr` after the initial meson setup). Then use ninja to build and install: ninja -C builddir/ install If you are installing into a system location you will need to run install separately, and as root.