33f0009de5
There is a Vivante GC1000 gpu in LS2K1000 and LS7A1000. LS7A1000 is a bridge chip made by Loongson corporation which act as north and/or south bridge of loongson's desktop and server level processor. It is equivalent to RS780E or something like that. In fact, the company use RS780E as bridge of LS3A3000 at its early stage, but as RS780E is out of stock long long time ago, the company have to made one by themself. More details can be read from its user manual[1]. This bridge chip typically use with LS3A3000, LS3A4000 and LS3A5000. LS3A3000 is 4 core 1.45gHz mips64r2 compatible cpu. LS3A4000 is 4 core 1.8gHz mips64r5 compatible cpu. LS3A5000 is 4 core 2.5gHz loongarch cpu, the company acclaim that loongarch a new archtecture with its instruction set is released[2]. LS2K1000 is a double core 1.0Ghz mips64r2 compatible SoC[3]. we need to enable it to test and developing driver on above listed archtecture. [1] https://loongson.github.io/LoongArch-Documentation/Loongson-7A1000-usermanual-EN.html [2] https://loongson.github.io/LoongArch-Documentation/Loongson-3A5000-usermanual-EN.html [3] https://wiki.debian.org/InstallingDebianOn/Lemote/Loongson2K1000 Signed-off-by: Sui Jingfeng <15330273260@189.cn> [Eric: rebase over meson changes, add ARM & ARC architectures, and drop "experimental" from the description] Signed-off-by: Eric Engestrom <eric@engestrom.ch> |
||
---|---|---|
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.