original_kernel

History

Torsten Duwe c19b3b0f6e KMS: fix EDID detailed timing frame rate When KMS has parsed an EDID "detailed timing", it leaves the frame rate zeroed. Consecutive (debug-) output of that mode thus yields 0 for vsync. This simple fix also speeds up future invocations of drm_mode_vrefresh(). While it is debatable whether this qualifies as a -stable fix I'd apply it for consistency's sake; drm_helper_probe_single_connector_modes() does the same thing already for all probed modes. Cc: stable@vger.kernel.org Signed-off-by: Torsten Duwe <duwe@lst.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2013-03-23 10:46:10 -07:00
..
ast	…
cirrus	…
exynos	…
gma500	…
i2c	…
i810	…
i915	…
mga	…
mgag200	…
nouveau	…
omapdrm	…
r128	…
radeon	…
savage	…
shmobile	…
sis	…
tdfx	…
tegra	…
tilcdc	…
ttm	…
udl	…
via	…
vmwgfx	…
Kconfig	…
Makefile	…
README.drm	…
ati_pcigart.c	…
drm_agpsupport.c	…
drm_auth.c	…
drm_buffer.c	…
drm_bufs.c	…
drm_cache.c	…
drm_context.c	…
drm_crtc.c	…
drm_crtc_helper.c	…
drm_debugfs.c	…
drm_dma.c	…
drm_dp_helper.c	…
drm_drv.c	…
drm_edid.c	KMS: fix EDID detailed timing frame rate	2013-03-23 10:46:10 -07:00
drm_edid_load.c	…
drm_encoder_slave.c	…
drm_fb_cma_helper.c	…
drm_fb_helper.c	…
drm_fops.c	…
drm_gem.c	…
drm_gem_cma_helper.c	…
drm_global.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_platform.c	…
drm_prime.c	…
drm_proc.c	…
drm_scatter.c	…
drm_stub.c	…
drm_sysfs.c	…
drm_trace.h	…
drm_trace_points.c	…
drm_usb.c	…
drm_vm.c	…

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