drm/freedreno
Rob Clark 49041c3613 freedreno: add support for FD_TIMESTAMP
Signed-off-by: Rob Clark <robclark@freedesktop.org>
2016-03-13 12:27:30 -04:00
..
kgsl freedreno: add support for FD_TIMESTAMP 2016-03-13 12:27:30 -04:00
msm freedreno: add support for FD_TIMESTAMP 2016-03-13 12:27:30 -04:00
Android.mk android: remove LOCAL_COPY_HEADERS* variables 2015-03-20 17:02:56 +00:00
Makefile.am freedreno: link against CLOCK_LIB 2015-04-29 17:30:17 +00:00
Makefile.sources drm: consolidate common list implementations (v2) 2015-08-05 13:47:48 -04:00
README freedreno: add freedreno DRM 2013-02-14 12:13:15 -05:00
freedreno-symbol-check freedreno: add API to get drm fd from fd_device 2015-09-04 11:08:04 -04:00
freedreno_bo.c freedreno: drop exported dmabuf fd tracking 2015-09-19 12:12:04 -04:00
freedreno_device.c freedreno: add API to get drm fd from fd_device 2015-09-04 11:08:04 -04:00
freedreno_drmif.h freedreno: add support for FD_TIMESTAMP 2016-03-13 12:27:30 -04:00
freedreno_pipe.c freedreno: add fd_pipe_wait_timeout() 2015-08-17 14:23:03 -04:00
freedreno_priv.h freedreno: drop exported dmabuf fd tracking 2015-09-19 12:12:04 -04:00
freedreno_ringbuffer.c drm: remove drm_public macro 2015-04-28 11:19:15 +01:00
freedreno_ringbuffer.h freedreno: annotate the device/bo/pipe/ringbuffer funcs as const data 2015-09-04 21:39:06 +01:00
libdrm_freedreno.pc.in freedreno: add freedreno DRM 2013-02-14 12:13:15 -05:00

README

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.