linux/drivers/char/drm
Al Viro 666002218d [PATCH] proc_mkdir() should be used to create procfs directories
A bunch of create_proc_dir_entry() calls creating directories had crept
in since the last sweep; converted to proc_mkdir().

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-29 08:46:26 -07:00
..
Kconfig drm: add savage driver 2005-08-07 15:43:54 +10:00
Makefile drm: add initial r300 3D support. 2005-08-16 20:43:16 +10:00
README.drm
ati_pcigart.c
drm.h drm: switch drm_handle_t to unsigned int 2005-08-05 22:13:15 +10:00
drmP.h [PATCH] PCI: remove CONFIG_PCI_NAMES 2005-09-08 14:57:23 -07:00
drm_agpsupport.c drm: fix a bad VERSION check. 2005-08-23 12:15:43 +10:00
drm_auth.c
drm_bufs.c drm: small cleanups 2005-09-05 21:33:44 +10:00
drm_context.c drm: small cleanups 2005-09-05 21:33:44 +10:00
drm_core.h
drm_dma.c
drm_drawable.c
drm_drv.c [PATCH] proc_mkdir() should be used to create procfs directories 2005-09-29 08:46:26 -07:00
drm_fops.c
drm_init.c
drm_ioc32.c
drm_ioctl.c drm: updated DRM map patch for 32/64 bit systems 2005-08-05 22:11:22 +10:00
drm_irq.c
drm_lock.c
drm_memory.c
drm_memory.h
drm_memory_debug.h
drm_os_linux.h
drm_pci.c drm: fix warning in drm_pci.c 2005-08-05 23:09:14 +10:00
drm_pciids.h drm: update pci ids for savage and via 2005-08-16 20:54:18 +10:00
drm_proc.c [PATCH] proc_mkdir() should be used to create procfs directories 2005-09-29 08:46:26 -07:00
drm_sarea.h
drm_scatter.c drm: updated DRM map patch for 32/64 bit systems 2005-08-05 22:11:22 +10:00
drm_stub.c
drm_sysfs.c drm: small cleanups 2005-09-05 21:33:44 +10:00
drm_vm.c drm: fixes for powerpc 2005-08-20 17:43:33 +10:00
ffb_context.c
ffb_drv.c drm: updated DRM map patch for 32/64 bit systems 2005-08-05 22:11:22 +10:00
ffb_drv.h
i810_dma.c drm: remove version.h and any version checks.. 2005-08-07 15:19:58 +10:00
i810_drm.h
i810_drv.c
i810_drv.h
i830_dma.c drm: remove version.h and any version checks.. 2005-08-07 15:19:58 +10:00
i830_drm.h
i830_drv.c
i830_drv.h
i830_irq.c
i915_dma.c
i915_drm.h
i915_drv.c
i915_drv.h
i915_ioc32.c
i915_irq.c
i915_mem.c
mga_dma.c drm: fix MGA on non AGP systems 2005-09-05 21:51:30 +10:00
mga_drm.h drm: updated DRM map patch for 32/64 bit systems 2005-08-05 22:11:22 +10:00
mga_drv.c
mga_drv.h
mga_ioc32.c drm: updated DRM map patch for 32/64 bit systems 2005-08-05 22:11:22 +10:00
mga_irq.c
mga_state.c
mga_ucode.h
mga_warp.c
r128_cce.c drm: updated DRM map patch for 32/64 bit systems 2005-08-05 22:11:22 +10:00
r128_drm.h drm: fix ioctl direction in r128 getparam 2005-08-05 21:52:18 +10:00
r128_drv.c
r128_drv.h
r128_ioc32.c
r128_irq.c
r128_state.c
r300_cmdbuf.c drm: add initial r300 3D support. 2005-08-16 20:43:16 +10:00
r300_reg.h drm: add initial r300 3D support. 2005-08-16 20:43:16 +10:00
radeon_cp.c drm: add initial r300 3D support. 2005-08-16 20:43:16 +10:00
radeon_drm.h drm: add initial r300 3D support. 2005-08-16 20:43:16 +10:00
radeon_drv.c
radeon_drv.h drm: add initial r300 3D support. 2005-08-16 20:43:16 +10:00
radeon_ioc32.c
radeon_irq.c
radeon_mem.c
radeon_state.c drm: add new texture upload code from r300 project 2005-08-20 17:40:04 +10:00
savage_bci.c drm: add savage driver 2005-08-07 15:43:54 +10:00
savage_drm.h drm: add savage driver 2005-08-07 15:43:54 +10:00
savage_drv.c drm: add savage driver 2005-08-07 15:43:54 +10:00
savage_drv.h drm: add savage driver 2005-08-07 15:43:54 +10:00
savage_state.c drm: add savage driver 2005-08-07 15:43:54 +10:00
sis_drm.h
sis_drv.c
sis_drv.h
sis_ds.c
sis_ds.h
sis_mm.c
tdfx_drv.c
tdfx_drv.h
via_3d_reg.h
via_dma.c
via_drm.h
via_drv.c
via_drv.h
via_ds.c
via_ds.h
via_irq.c
via_map.c
via_mm.c
via_mm.h
via_verifier.c
via_verifier.h
via_video.c

README.drm

************************************************************
* For the very latest on DRI development, please see:      *
*     http://dri.sourceforge.net/                          *
************************************************************

The Direct Rendering Manager (drm) is a device-independent kernel-level
device driver that provides support for the XFree86 Direct Rendering
Infrastructure (DRI).

The DRM supports the Direct Rendering Infrastructure (DRI) in four major
ways:

    1. The DRM provides synchronized access to the graphics hardware via
       the use of an optimized two-tiered lock.

    2. The DRM enforces the DRI security policy for access to the graphics
       hardware by only allowing authenticated X11 clients access to
       restricted regions of memory.

    3. The DRM provides a generic DMA engine, complete with multiple
       queues and the ability to detect the need for an OpenGL context
       switch.

    4. The DRM is extensible via the use of small device-specific modules
       that rely extensively on the API exported by the DRM module.


Documentation on the DRI is available from:
    http://precisioninsight.com/piinsights.html

For specific information about kernel-level support, see:

    The Direct Rendering Manager, Kernel Support for the Direct Rendering
    Infrastructure
    http://precisioninsight.com/dr/drm.html

    Hardware Locking for the Direct Rendering Infrastructure
    http://precisioninsight.com/dr/locking.html

    A Security Analysis of the Direct Rendering Infrastructure
    http://precisioninsight.com/dr/security.html

************************************************************
* For the very latest on DRI development, please see:      *
*     http://dri.sourceforge.net/                          *
************************************************************