drm/freedreno
Rob Clark 0b89e2730c freedreno: add handle and name tracking
Due to the evil userspace buffer tracking we have to do, and hacks for
creating GEM buffer from fbdev/scanout, "evil-twin" fd_bo objects are
problematic.  So introduce hashtable tracking of bo's and dev's, to
avoid getting duplicate fd_bo ptrs for the same underlying gem object,
in particular when importing via flink name.

Signed-off-by: Rob Clark <robclark@freedesktop.org>
2013-05-15 15:34:15 -04:00
..
Makefile.am makefiles: Add missing headers. 2013-03-27 14:06:56 +01:00
README freedreno: add freedreno DRM 2013-02-14 12:13:15 -05:00
freedreno_bo.c freedreno: add handle and name tracking 2013-05-15 15:34:15 -04:00
freedreno_device.c freedreno: add handle and name tracking 2013-05-15 15:34:15 -04:00
freedreno_drmif.h freedreno: add handle and name tracking 2013-05-15 15:34:15 -04:00
freedreno_pipe.c freedreno: add synchronization between mesa and ddx 2013-04-25 17:33:59 -04:00
freedreno_priv.h freedreno: add handle and name tracking 2013-05-15 15:34:15 -04:00
freedreno_ringbuffer.c freedreno: add synchronization between mesa and ddx 2013-04-25 17:33:59 -04:00
freedreno_ringbuffer.h freedreno: add shifted reloc 2013-04-13 08:13:57 -04:00
kgsl_drm.h freedreno: add freedreno DRM 2013-02-14 12:13:15 -05:00
libdrm_freedreno.pc.in freedreno: add freedreno DRM 2013-02-14 12:13:15 -05:00
list.h freedreno: add freedreno DRM 2013-02-14 12:13:15 -05:00
msm_kgsl.h 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.