linux/drivers/gpu/drm
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 alpha, drm: Remove obsolete Alpha support in MGA DRM code 2011-06-14 09:32:56 +10:00
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 savage: remove unnecessary if statement 2011-06-14 09:29:12 +10:00
sis treewide: fix potentially dangerous trailing ';' in #defined values/expressions 2011-07-21 14:10:00 +02:00
tdfx
ttm drm/ttm: request zeroed system memory pages for new TT buffer objects 2011-09-14 13:34:51 +01:00
via
vmwgfx drivers: use kzalloc/kcalloc instead of 'kmalloc+memset', where possible 2011-07-25 20:57:13 -07:00
Kconfig
Makefile
README.drm
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_buffer.c
drm_bufs.c drm: Compare only lower 32 bits of framebuffer map offsets 2011-06-14 11:09:54 +10:00
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: bpp and depth changes require full mode sets 2011-07-07 13:20:49 -07:00
drm_debugfs.c drm/debugfs: Initialise empty variable 2011-08-04 14:38:52 +01:00
drm_dma.c
drm_dp_i2c_helper.c
drm_drv.c
drm_edid.c drm: Separate EDID Header Check from EDID Block Check 2011-08-04 14:39:35 +01:00
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/gem: add support for private objects 2011-07-25 12:07:15 +01:00
drm_global.c
drm_hashtab.c
drm_info.c
drm_ioc32.c drivers/gpu/drm: use printk_ratelimited instead of printk_ratelimit 2011-06-16 16:32:15 +10:00
drm_ioctl.c
drm_irq.c drm: Add NULL check about irq functions 2011-08-04 14:39:21 +01:00
drm_lock.c
drm_memory.c
drm_mm.c
drm_modes.c DRM: clean up and document parsing of video= parameter 2011-07-25 12:02:26 +01:00
drm_pci.c drm: populate irq_by_busid-member for pci 2011-06-16 16:26:45 +10:00
drm_platform.c drm: platform multi-device support 2011-07-15 06:52:58 +01:00
drm_proc.c
drm_scatter.c drivers: use kzalloc/kcalloc instead of 'kmalloc+memset', where possible 2011-07-25 20:57:13 -07:00
drm_sman.c
drm_stub.c
drm_sysfs.c
drm_trace.h
drm_trace_points.c
drm_usb.c
drm_vm.c alpha/drm: Cleanup Alpha support in DRM generic code 2011-06-14 09:31:37 +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