linux_dsm_epyc7002/drivers/gpu/drm
ling.ma@intel.com febc7694a5 drm/i915: Disable VGA output when doing DRM_MODE_DPMS_OFF.
Signed-off-by: Ma Ling <ling.ma@intel.com>
Signed-off-by: Eric Anholt <eric@anholt.net>
2009-07-07 11:49:01 -07:00
..
i810 drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
i830 drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
i915 drm/i915: Disable VGA output when doing DRM_MODE_DPMS_OFF. 2009-07-07 11:49:01 -07:00
mga drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
r128 drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
radeon drm/radeon: fix driver initialization order so radeon kms can be builtin 2009-06-24 16:11:06 +10:00
savage drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
sis drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
tdfx
ttm drm: remove unused #include <linux/version.h>'s 2009-06-24 16:31:50 +10:00
via drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
ati_pcigart.c
drm_agpsupport.c agp: switch AGP to use page array instead of unsigned long array 2009-06-19 10:21:42 +10:00
drm_auth.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_bufs.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_cache.c
drm_context.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_crtc_helper.c
drm_crtc.c
drm_debugfs.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_dma.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_drawable.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_drv.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_edid.c drm: Fix shifts which were miscalculated when converting from bitfields. 2009-06-24 16:11:04 +10:00
drm_fops.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_gem.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_hashtab.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_info.c
drm_ioc32.c
drm_ioctl.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_irq.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_lock.c
drm_memory.c agp: switch AGP to use page array instead of unsigned long array 2009-06-19 10:21:42 +10:00
drm_mm.c drm: Apply "Memory fragmentation from lost alignment blocks" 2009-06-19 09:01:12 +10:00
drm_modes.c
drm_pci.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_proc.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_scatter.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_sman.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_stub.c drm: Remove memory debugging infrastructure. 2009-06-18 13:00:33 -07:00
drm_sysfs.c Driver Core: drm: add nodename for drm devices 2009-06-15 21:30:26 -07:00
drm_vm.c agp: switch AGP to use page array instead of unsigned long array 2009-06-19 10:21:42 +10:00
Kconfig drm/i915: Add missing dependency on Intel AGP support. 2009-06-21 22:13:38 -07:00
Makefile drm/radeon: fix driver initialization order so radeon kms can be builtin 2009-06-24 16:11:06 +10:00
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