mesa-drm/linux-core
Gareth Hughes 7630a6397c Hardware accelerated rendering for the Rage Pro.
Client-side PIO with texturing, enough to play Q3A 'Fastest'. Multitexture
    not working correctly at this stage, no lines or points, bits of state
    missing etc. Should run most of the Mesa demos.
I will make a full post to dri-devel regarding the current state of the
    driver, so please see that for more information.
2000-12-17 15:32:33 +00:00
..
drmP.h Sync with Linux 2.4.0-test11-pre5 Provide backward compatibility tested 2000-11-15 15:47:51 +00:00
i810_dma.c Audit calls to schedule() Remove tags from files shared with Linux kernel 2000-09-29 01:47:11 +00:00
i810_drm.h applied Jeff's xf86cvs-I810copy.patch 2000-07-13 18:47:48 +00:00
i810_drv.c Sync with Linux 2.4.0-test11-pre5 Provide backward compatibility tested 2000-11-15 15:47:51 +00:00
i810_drv.h Audit calls to schedule() Remove tags from files shared with Linux kernel 2000-09-29 01:47:11 +00:00
mach64_drv.c Hardware accelerated rendering for the Rage Pro. 2000-12-17 15:32:33 +00:00
Makefile.kernel Create and map DMA buffers. Includes refactoring of buffer setup code in 2000-12-13 10:30:26 +00:00
mga_drv.c New templated DRM code. First pass at extracting out a lot of the common 2000-11-27 15:30:26 +00:00
r128_drv.c New templated DRM code. First pass at extracting out a lot of the common 2000-11-27 15:30:26 +00:00
README.drm More changes for sync with Linux 2.4.0-test9-pre7 2000-09-29 02:05:41 +00:00
sis_drv.c Sync with Linux 2.4.0-test11-pre5 Provide backward compatibility tested 2000-11-15 15:47:51 +00:00
tdfx_drv.c New templated DRM code. First pass at extracting out a lot of the common 2000-11-27 15:30:26 +00:00

************************************************************
* 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/                          *
************************************************************