linux

q3k/linux

History

Jesse Barnes 317c35d144 separate i915 suspend/resume functions into their own file [Patch against drm-next. Consider this a trial balloon for our new Linux development model.] This is a big chunk of code. Separating it out makes it easier to change without churn on the main i915_drv.c file (and there will be churn as we fix bugs and add things like kernel mode setting). Also makes it easier to share this file with BSD. Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Dave Airlie <airlied@redhat.com>		2008-10-18 07:10:11 +10:00
..
i810
i830
i915	separate i915 suspend/resume functions into their own file	2008-10-18 07:10:11 +10:00
mga
r128
radeon	radeon: fix writeback across suspend/resume.	2008-10-18 07:10:11 +10:00
savage
sis	SiS DRM: fix a pointer cast warning	2008-10-18 07:10:10 +10:00
tdfx
via
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_bufs.c
drm_context.c
drm_dma.c
drm_drawable.c
drm_drv.c	drm: make drm_minors_cleanup() static	2008-07-26 12:00:11 -07:00
drm_fops.c
drm_hashtab.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c	i915: Add support for MSI and interrupt mitigation.	2008-10-18 07:10:10 +10:00
drm_lock.c	drm: don't set the signal blocker on the master process.	2008-08-25 06:35:33 +10:00
drm_memory.c
drm_mm.c
drm_pci.c
drm_proc.c
drm_scatter.c
drm_sman.c
drm_stub.c
drm_sysfs.c	drm: fix sysfs error path.	2008-10-18 07:10:11 +10:00
drm_vm.c
Kconfig	FB_SIS=m, DRM_SIS=y is not a legal configuration.	2008-10-18 07:10:11 +10: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