• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

kgsl/22-Nov-2023-1,7051,137

msm/22-Nov-2023-1,029632

Android.mkD22-Nov-2023665 3120

Makefile.amD22-Nov-2023804 2922

Makefile.sourcesD22-Nov-2023507 2724

READMED22-Nov-2023971 1715

freedreno_bo.cD22-Nov-20239.3 KiB428291

freedreno_device.cD22-Nov-20234.4 KiB163100

freedreno_drmif.hD22-Nov-20233.7 KiB11358

freedreno_pipe.cD22-Nov-20232.1 KiB7739

freedreno_priv.hD22-Nov-20235.1 KiB173108

freedreno_ringbuffer.cD22-Nov-20233.9 KiB14790

freedreno_ringbuffer.hD22-Nov-20233.1 KiB8945

libdrm_freedreno.pc.inD22-Nov-2023331 1210

list.hD22-Nov-20234.4 KiB13884

README

1Note that current msm kernel driver is a bit strange.  It provides a
2DRM interface for GEM, which is basically sufficient to have DRI2
3working.  But it does not provide KMS.  And interface to 2d and 3d
4cores is via different other devices (/dev/kgsl-*).  This is not
5quite how I'd write a DRM driver, but at this stage it is useful for
6xf86-video-freedreno and fdre (and eventual gallium driver) to be
7able to work on existing kernel driver from QCOM, to allow to
8capture cmdstream dumps from the binary blob drivers without having
9to reboot.  So libdrm_freedreno attempts to hide most of the crazy.
10The intention is that when there is a proper kernel driver, it will
11be mostly just changes in libdrm_freedreno to adapt the gallium
12driver and xf86-video-freedreno (ignoring the fbdev->KMS changes).
13
14So don't look at freedreno as an example of how to write a libdrm
15module or a DRM driver.. it is just an attempt to paper over a non-
16standard kernel driver architecture.
17