kernel-ark

History

Dave Airlie dfab11542f drm: rationalise some pci ids This is the start of some work from Roland Scheidegger to align the X DDX pci ids and the drm ones, however we don't want to put r300 ids in the kernel just yet, they destabilise a few machines. From: Roland Scheidegger (via DRM CVS) Signed-off-by: Dave Airlie <airlied@linux.ie>		2006-03-19 20:01:37 +11:00
..
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_bufs.c	drm: fixup PCI DMA support	2006-03-19 18:56:12 +11:00
drm_context.c
drm_core.h
drm_dma.c	drm: fixup PCI DMA support	2006-03-19 18:56:12 +11:00
drm_drawable.c
drm_drv.c
drm_fops.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c
drm_lock.c
drm_memory_debug.h
drm_memory.c
drm_memory.h
drm_os_linux.h
drm_pci.c	drm: fixup PCI DMA support	2006-03-19 18:56:12 +11:00
drm_pciids.h	drm: rationalise some pci ids	2006-03-19 20:01:37 +11:00
drm_proc.c
drm_sarea.h
drm_scatter.c
drm_stub.c
drm_sysfs.c
drm_vm.c
drm.h
drmP.h	drm: fixup PCI DMA support	2006-03-19 18:56:12 +11:00
ffb_context.c
ffb_drv.c
ffb_drv.h
i810_dma.c
i810_drm.h
i810_drv.c
i810_drv.h
i830_dma.c
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	drm: fixup i915 interrupt on X server exit	2006-02-18 15:17:04 +11:00
i915_mem.c
Kconfig
Makefile
mga_dma.c
mga_drm.h
mga_drv.c
mga_drv.h
mga_ioc32.c
mga_irq.c
mga_state.c
mga_ucode.h
mga_warp.c
r128_cce.c
r128_drm.h
r128_drv.c
r128_drv.h
r128_ioc32.c
r128_irq.c
r128_state.c
r300_cmdbuf.c	drm: Add general-purpose packet for manipulating scratch registers (r300)	2006-03-19 19:45:26 +11:00
r300_reg.h	drm: update r300 register names	2006-03-19 19:12:10 +11:00
radeon_cp.c	drm: rework radeon memory map (radeon 1.23)	2006-03-19 19:37:55 +11:00
radeon_drm.h	drm: Add general-purpose packet for manipulating scratch registers (r300)	2006-03-19 19:45:26 +11:00
radeon_drv.c
radeon_drv.h	drm: rationalise some pci ids	2006-03-19 20:01:37 +11:00
radeon_ioc32.c
radeon_irq.c
radeon_mem.c
radeon_state.c	drm: rework radeon memory map (radeon 1.23)	2006-03-19 19:37:55 +11:00
README.drm
savage_bci.c
savage_drm.h
savage_drv.c
savage_drv.h
savage_state.c
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_dmablit.c
via_dmablit.h
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/                          *
************************************************************