1
linux/drivers/gpu/drm
Chris Wilson cb8ea7527b drm/i915: Use i2c bit banging instead of GMBUS
There are several reported instances of GMBUS failing to successfully
read the EDID, so revert back to bit banging until the issue is
resolved.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=30371
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
2010-09-28 13:35:47 +01:00
..
i2c
i810
i830
i915 drm/i915: Use i2c bit banging instead of GMBUS 2010-09-28 13:35:47 +01:00
mga
nouveau Merge branch 'drm-intel-fixes' into HEAD 2010-09-21 11:19:32 +01:00
r128
radeon Merge branch 'drm-intel-fixes' into HEAD 2010-09-21 11:19:32 +01:00
savage
sis
tdfx
ttm
via
vmwgfx Merge branch 'drm-intel-fixes' into HEAD 2010-09-21 11:19:32 +01:00
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_buffer.c
drm_bufs.c
drm_cache.c
drm_context.c
drm_crtc_helper.c drm: Use a nondestructive mode for output detect when polling (v2) 2010-09-14 20:38:48 +10:00
drm_crtc.c
drm_debugfs.c
drm_dma.c
drm_dp_i2c_helper.c
drm_drv.c
drm_edid_modes.h
drm_edid.c drm/i915: use GMBUS to manage i2c links 2010-09-18 15:46:19 +01:00
drm_encoder_slave.c
drm_fb_helper.c
drm_fops.c
drm_gem.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: fix race between driver loading and userspace open. 2010-09-14 20:39:04 +10:00
drm_platform.c drm: fix race between driver loading and userspace open. 2010-09-14 20:39:04 +10:00
drm_proc.c
drm_scatter.c
drm_sman.c
drm_stub.c
drm_sysfs.c drm: Use a nondestructive mode for output detect when polling 2010-09-13 20:29:11 +10:00
drm_trace_points.c
drm_trace.h
drm_vm.c
Kconfig
Makefile
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