mirror of
https://gitlab.freedesktop.org/mesa/drm.git
synced 2025-12-23 23:40:10 +01:00
the 2D driver initializes MC_FB_LOCATION and related registers sanely
the DRM deduces the layout from these registers
clients use the new SETPARAM ioctl to tell the DRM where they think the
framebuffer is located in the card's address space
the DRM uses all this information to check client state and fix it up if
necessary
This is a prerequisite for things like direct rendering with IGP chips and
video capturing.
|
||
|---|---|---|
| .. | ||
| ati_pcigart.h | ||
| Config.in | ||
| Doxyfile | ||
| drm.h | ||
| drm_agpsupport.h | ||
| drm_auth.h | ||
| drm_bufs.h | ||
| drm_context.h | ||
| drm_dma.h | ||
| drm_drawable.h | ||
| drm_drv.h | ||
| drm_fops.h | ||
| drm_init.h | ||
| drm_ioctl.h | ||
| drm_irq.h | ||
| drm_lock.h | ||
| drm_memory.h | ||
| drm_memory_debug.h | ||
| drm_os_linux.h | ||
| drm_proc.h | ||
| drm_scatter.h | ||
| drm_stub.h | ||
| drm_vm.h | ||
| drmP.h | ||
| gamma.h | ||
| gamma_context.h | ||
| gamma_dma.c | ||
| gamma_drm.h | ||
| gamma_drv.c | ||
| gamma_drv.h | ||
| gamma_lists.h | ||
| gamma_lock.h | ||
| gamma_old_dma.h | ||
| i810.h | ||
| i810_dma.c | ||
| i810_drm.h | ||
| i810_drv.c | ||
| i810_drv.h | ||
| i830.h | ||
| i830_dma.c | ||
| i830_drm.h | ||
| i830_drv.c | ||
| i830_drv.h | ||
| i830_irq.c | ||
| Kconfig | ||
| Makefile.kernel | ||
| Makefile.linux | ||
| mga_drv.c | ||
| r128_drv.c | ||
| radeon_drv.c | ||
| README.drm | ||
| sis_drv.c | ||
| tdfx_drv.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/ *
************************************************************