linux

q3k/linux

History

Dave Airlie 97f23b3d85 drm/radeon/kms: don't print error on -ERESTARTSYS. We can get this if the user moves the mouse when we are waiting to move some stuff around in the validate. Don't fail. Cc: stable@kernel.org Signed-off-by: Dave Airlie <airlied@redhat.com>		2010-03-31 13:11:35 +10:00
..
i2c
i810
i830
i915	Merge branch 'gpu-switcher' of /ssd/git//linux-2.6 into drm-next-stage	2010-03-01 16:22:38 +10:00
mga
nouveau	Merge remote branch 'nouveau/for-airlied' into drm-linus	2010-03-15 11:07:33 +10:00
r128
radeon	drm/radeon/kms: don't print error on -ERESTARTSYS.	2010-03-31 13:11:35 +10:00
savage
sis
tdfx
ttm	drm: "kobject_init/kobject_add" -> "kobject_init_and_add".	2010-03-15 10:32:09 +10:00
via
vmwgfx	drm/vmwgfx: depends on FB	2010-03-15 10:35:04 +10:00
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_buffer.c	drm: Add generic multipart buffer.	2010-02-23 09:46:20 +10:00
drm_bufs.c
drm_cache.c
drm_context.c
drm_crtc.c
drm_crtc_helper.c	drm: remove the EDID blob stored in the EDID property when it is disconnected	2010-03-15 10:36:21 +10:00
drm_debugfs.c
drm_dma.c
drm_dp_i2c_helper.c
drm_drawable.c
drm_drv.c
drm_edid.c	drm/edid: allow certain bogus edids to hit a fixup path rather than fail	2010-03-15 10:58:17 +10:00
drm_encoder_slave.c
drm_fb_helper.c
drm_fops.c
drm_gem.c
drm_hashtab.c
drm_info.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c
drm_lock.c
drm_memory.c
drm_mm.c
drm_modes.c
drm_pci.c
drm_proc.c
drm_scatter.c
drm_sman.c
drm_stub.c
drm_sysfs.c
drm_vm.c
Kconfig
Makefile	drm: Add generic multipart buffer.	2010-02-23 09:46:20 +10:00
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