kernel-ark

History

Chris Wilson b6651458d3 drm/i915: Invalidate the to-ring, flush the old-ring when updating domains When the object has been written to by the gpu it remains on the ring until its flush has been retired. However, when the object is moving to the ring and the associated cache needs to be invalidated, we need to perform the flush on the target ring, not the one it came from (which is NULL in the reported case and so the flush was entirely absent). Reported-by: Peter Clifton <pcjc2@cam.ac.uk> Reported-and-tested-by: Alexey Fisher <bug-track@fisher-privat.net> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>		2010-10-23 11:07:21 +01:00
..
i2c
i810	Merge remote branch 'korg/drm-fixes' into drm-vmware-next	2010-10-06 11:10:48 +10:00
i830	Merge remote branch 'korg/drm-fixes' into drm-vmware-next	2010-10-06 11:10:48 +10:00
i915	drm/i915: Invalidate the to-ring, flush the old-ring when updating domains	2010-10-23 11:07:21 +01:00
mga
nouveau	drm, kdb, kms: Change mode_set_base_atomic() enter argument to be an enum	2010-10-19 14:13:33 +10:00
r128
radeon	drm, kdb, kms: Change mode_set_base_atomic() enter argument to be an enum	2010-10-19 14:13:33 +10:00
savage
sis
tdfx
ttm	drm/ttm: Simplify ttm_bo_wait_unreserved	2010-10-19 14:12:27 +10:00
via
vmwgfx	Merge remote branch 'nouveau/for-airlied' of ../drm-nouveau-next into drm-core-next	2010-10-06 12:57:11 +10:00
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_buffer.c	drm: fix trivial coding errors	2010-09-24 10:10:23 +10:00
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: vmwgfx: Add a struct drm_file parameter to the dirty framebuffer callback	2010-10-06 11:29:41 +10:00
drm_debugfs.c	drm: Move the GTT accounting to i915	2010-10-01 14:45:20 +01:00
drm_dma.c
drm_dp_i2c_helper.c
drm_drv.c
drm_edid_modes.h
drm_edid.c	drm/edid: add helper function to detect monitor audio capability	2010-10-19 09:17:32 +01:00
drm_encoder_slave.c
drm_fb_helper.c	drm, kdb, kms: Change mode_set_base_atomic() enter argument to be an enum	2010-10-19 14:13:33 +10:00
drm_fops.c
drm_gem.c	Merge remote branch 'korg/drm-fixes' into drm-vmware-next	2010-10-06 11:10:48 +10:00
drm_global.c
drm_hashtab.c
drm_info.c	Merge remote branch 'korg/drm-fixes' into drm-vmware-next	2010-10-06 11:10:48 +10:00
drm_ioc32.c
drm_ioctl.c
drm_irq.c
drm_lock.c	drm: readd drm_lock_free in drm_unlock	2010-09-26 13:35:49 +10:00
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: Move the GTT accounting to i915	2010-10-01 14:45:20 +01:00
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	Merge remote branch 'korg/drm-fixes' into drm-vmware-next	2010-10-06 11:10:48 +10:00
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