xenocara/lib/libdrm/freedreno
2015-08-21 23:55:36 +00:00
..
kgsl Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
msm Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
Android.mk Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno_bo.c Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno_device.c Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno_drmif.h Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno_pipe.c Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno_priv.h Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno_ringbuffer.c Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno_ringbuffer.h Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
freedreno-symbol-check Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
libdrm_freedreno.pc.in Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
Makefile.am Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
Makefile.in Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
Makefile.sources Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00
README Import libdrm 2.4.64 2015-08-21 23:55:36 +00:00

Note that current msm kernel driver is a bit strange.  It provides a
DRM interface for GEM, which is basically sufficient to have DRI2
working.  But it does not provide KMS.  And interface to 2d and 3d
cores is via different other devices (/dev/kgsl-*).  This is not
quite how I'd write a DRM driver, but at this stage it is useful for
xf86-video-freedreno and fdre (and eventual gallium driver) to be
able to work on existing kernel driver from QCOM, to allow to
capture cmdstream dumps from the binary blob drivers without having
to reboot.  So libdrm_freedreno attempts to hide most of the crazy.
The intention is that when there is a proper kernel driver, it will
be mostly just changes in libdrm_freedreno to adapt the gallium
driver and xf86-video-freedreno (ignoring the fbdev->KMS changes).

So don't look at freedreno as an example of how to write a libdrm
module or a DRM driver.. it is just an attempt to paper over a non-
standard kernel driver architecture.