drm/freedreno
Rob Clark 8279c8fb49 freedreno: add fd_device_new_dup()
There seem to be some cases (I've noticed this switching resolution in
some games, for example) where the fd can get closed() before the device
and all it's bo's are destroyed.  Which, if the drm device is opened
again and bo's are allocated with the same handles, results that when
the first pipe_screen/pipe_context is destroyed causes the first dev to
close handles for bo's allocated by the second device.

The easy solution to that is to add a mode where the fd_device creates
it's own private fd (a dup()).

Signed-off-by: Rob Clark <robclark@freedesktop.org>
2014-01-12 09:00:51 -05:00
..
kgsl freedreno/kgsl: fix crash introduced w/ bo-cache 2014-01-07 11:33:54 -05:00
msm freedreno: allow IB to different ringbuffer 2014-01-07 11:33:54 -05:00
Makefile.am freedreno: set automake options to include subdir-objects 2013-08-30 11:37:14 -04:00
README freedreno: add freedreno DRM 2013-02-14 12:13:15 -05:00
freedreno_bo.c freedreno: add bo cache 2013-12-13 15:48:10 -05:00
freedreno_device.c freedreno: add fd_device_new_dup() 2014-01-12 09:00:51 -05:00
freedreno_drmif.h freedreno: add fd_device_new_dup() 2014-01-12 09:00:51 -05:00
freedreno_pipe.c freedreno: support either kgsl or msm 2013-08-28 15:50:15 -04:00
freedreno_priv.h freedreno: add fd_device_new_dup() 2014-01-12 09:00:51 -05:00
freedreno_ringbuffer.c freedreno: allow IB to different ringbuffer 2014-01-07 11:33:54 -05:00
freedreno_ringbuffer.h freedreno: allow IB to different ringbuffer 2014-01-07 11:33:54 -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

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.