android_kernel_xiaomi_sm7250

History

Kay Sievers 2ead054cd2 drm: struct device - replace bus_id with dev_name(), dev_set_name() Cc: airlied@linux.ie Acked-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>		2009-03-24 16:38:22 -07:00
..
i810
i830
i915	drm/i915: fix 945 fence register writes for fence 8 and above.	2009-03-11 11:02:06 -07:00
mga
r128
radeon	drm/radeon: update sarea copies of last_ variables on resume.	2009-02-20 12:29:05 +10:00
savage
sis
tdfx
via
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_bufs.c	drm: Wake up all lock waiters when the master disappears.	2009-03-03 09:49:54 +10:00
drm_cache.c
drm_context.c
drm_crtc_helper.c	drm: disable encoders before re-routing them	2009-02-25 14:42:23 +10:00
drm_crtc.c
drm_dma.c
drm_drawable.c
drm_drv.c
drm_edid.c	drm: edid revision 0 is valid	2009-02-25 14:47:05 +10:00
drm_fops.c	drm: Avoid client deadlocks when the master disappears.	2009-03-03 09:50:20 +10:00
drm_gem.c
drm_hashtab.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c	drm: Correct unbalanced drm_vblank_put() during mode setting.	2009-02-25 14:45:50 +10:00
drm_lock.c	drm: Avoid client deadlocks when the master disappears.	2009-03-03 09:50:20 +10:00
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: fix double lock typo	2009-03-04 21:49:14 +10:00
drm_sysfs.c	drm: struct device - replace bus_id with dev_name(), dev_set_name()	2009-03-24 16:38:22 -07:00
drm_vm.c
Kconfig
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