linux

History

Chris Wilson 3e49c4f4cf drm: Free the object ref on error. Ensure that the object is unreferenced if we fail to allocate during drm_gem_flink_ioctl(). Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Eric Anholt <eric@anholt.net> Signed-off-by: Dave Airlie <airlied@linux.ie>		2009-02-20 12:21:08 +10:00
..
i810
i830
i915	drm/i915: Storage class should be before const qualifier	2009-02-20 12:21:08 +10:00
mga
r128
radeon	drm/radeon: fix ioremap conflict with AGP mappings	2009-02-08 21:37:24 +10:00
savage
sis
tdfx
via
ati_pcigart.c
drm_agpsupport.c	drm: stash AGP include under the do-we-have-AGP ifdef	2009-01-22 22:27:11 +10:00
drm_auth.c
drm_bufs.c
drm_cache.c
drm_context.c
drm_crtc_helper.c	drm: handle depth & bpp changes correctly	2009-01-16 18:40:57 +10:00
drm_crtc.c	drm: create mode_config idr lock	2009-01-22 17:53:05 +10:00
drm_dma.c
drm_drawable.c
drm_drv.c	drm: fix leak of device mappings since multi-master changes.	2009-01-19 17:17:58 +10:00
drm_edid.c	drm: don't whine about not reading EDID data	2009-01-22 22:23:53 +10:00
drm_fops.c
drm_gem.c	drm: Free the object ref on error.	2009-02-20 12:21:08 +10:00
drm_hashtab.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c	drm/i915: capture last_vblank count at IRQ uninstall time too	2009-02-08 21:40:51 +10:00
drm_lock.c
drm_memory.c	drm/radeon: fix ioremap conflict with AGP mappings	2009-02-08 21:37:24 +10:00
drm_mm.c
drm_modes.c
drm_pci.c
drm_proc.c
drm_scatter.c
drm_sman.c
drm_stub.c	drm: fix leak of device mappings since multi-master changes.	2009-01-19 17:17:58 +10:00
drm_sysfs.c
drm_vm.c
Kconfig	fbdev/drm: fix Kconfig submenu mess in "Graphics support"	2009-02-18 15:37:56 -08:00
Makefile
README.drm

README.drm

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

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://dri.freedesktop.org/wiki/Documentation
    http://sourceforge.net/project/showfiles.php?group_id=387
    http://dri.sourceforge.net/doc/

For specific information about kernel-level support, see:

    The Direct Rendering Manager, Kernel Support for the Direct Rendering
    Infrastructure
    http://dri.sourceforge.net/doc/drm_low_level.html

    Hardware Locking for the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/hardware_locking_low_level.html

    A Security Analysis of the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/security_low_level.html