linux-stable-rt

History

Alex Deucher 12d5180bd7 drm/radeon/kms: fix channel_remap setup (v2) Most asics just use the hw default value which requires no explicit programming. For those that need a different value, the vbios will program it properly. As such, there's no need to program these registers explicitly in the driver. Changing MC_SHARED_CHREMAP requires a reload of all data in vram otherwise its contents will be scambled. Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=40103 v2: drop now unused channel_remap functions. Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Cc: stable@kernel.org Signed-off-by: Dave Airlie <airlied@redhat.com>		2011-10-04 17:24:14 +01:00
..
i2c	…
i810	…
i915	drm/i915: FBC off for ironlake and older, otherwise on by default	2011-09-21 15:03:11 -07:00
mga	…
nouveau	drm/nv04/crtc: Bail out if FB is not bound to crtc	2011-09-09 17:24:21 +10:00
r128	…
radeon	drm/radeon/kms: fix channel_remap setup (v2)	2011-10-04 17:24:14 +01:00
savage	…
sis	…
tdfx	…
ttm	drm/ttm: request zeroed system memory pages for new TT buffer objects	2011-09-14 13:34:51 +01:00
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: Fix the number of connector and encoder to cleanup functions	2011-08-29 11:47:35 +01:00
drm_crtc_helper.c	…
drm_debugfs.c	…
drm_dma.c	…
drm_dp_i2c_helper.c	…
drm_drv.c	…
drm_edid.c	…
drm_edid_modes.h	…
drm_encoder_slave.c	…
drm_fb_helper.c	drm: Remove duplicate "return" statement	2011-09-09 09:11:44 +01:00
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_platform.c	…
drm_proc.c	…
drm_scatter.c	…
drm_sman.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