mirror of
https://gitlab.freedesktop.org/mesa/drm.git
synced 2026-05-14 05:18:04 +02:00
81f4398ed7
turning CCE off when the X server actually has to do some 2D rendering.
We test if the CCE is running at the start of each accel routine, and
if so we shut it down. If we've shut it down, we start it up again in
LeaveServer(). An extra if statement in the accel routines is worth it,
IMNSHO.
Updates to the elt path code. Allow indirect buffer firing to specify start
and end parameters for buffer reuse. DRM ioctls and wrappers adjusted
accordingly. Still disabled by default.
|
||
|---|---|---|
| .. | ||
| agpsupport.c | ||
| auth.c | ||
| bufs.c | ||
| compat-pre24.h | ||
| context.c | ||
| ctxbitmap.c | ||
| dma.c | ||
| drawable.c | ||
| drm.h | ||
| drmP.h | ||
| fops.c | ||
| gamma_dma.c | ||
| gamma_drv.c | ||
| gamma_drv.h | ||
| i810_bufs.c | ||
| i810_context.c | ||
| i810_dma.c | ||
| i810_drm.h | ||
| i810_drv.c | ||
| i810_drv.h | ||
| init.c | ||
| ioctl.c | ||
| lists.c | ||
| lock.c | ||
| Makefile.kernel | ||
| Makefile.linux | ||
| memory.c | ||
| mga_bufs.c | ||
| mga_context.c | ||
| mga_dma.c | ||
| mga_drm.h | ||
| mga_drv.c | ||
| mga_drv.h | ||
| mga_state.c | ||
| picker.c | ||
| proc.c | ||
| r128_bufs.c | ||
| r128_cce.c | ||
| r128_context.c | ||
| r128_drm.h | ||
| r128_drv.c | ||
| r128_drv.h | ||
| r128_state.c | ||
| README.drm | ||
| sis_context.c | ||
| sis_drm.h | ||
| sis_drv.c | ||
| sis_drv.h | ||
| sis_ds.c | ||
| sis_ds.h | ||
| sis_mm.c | ||
| tdfx_context.c | ||
| tdfx_drv.c | ||
| tdfx_drv.h | ||
| vm.c | ||
************************************************************
* For the very latest on DRI development, please see: *
* http://dri.sourceforge.net/ *
************************************************************
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://precisioninsight.com/piinsights.html
For specific information about kernel-level support, see:
The Direct Rendering Manager, Kernel Support for the Direct Rendering
Infrastructure
http://precisioninsight.com/dr/drm.html
Hardware Locking for the Direct Rendering Infrastructure
http://precisioninsight.com/dr/locking.html
A Security Analysis of the Direct Rendering Infrastructure
http://precisioninsight.com/dr/security.html
************************************************************
* For the very latest on DRI development, please see: *
* http://dri.sourceforge.net/ *
************************************************************