linux

History

David Howells 6bb9e4bff5 SiS DRM: fix the memory allocator if the SIS FB is built as a module Fix the SIS DRM memory allocator if the SIS FB built as a module. The SIS DRM code initialises the mm allocation hooks, but _only_ if the SIS FB is not built as a module because it depends on CONFIG_FB_SIS, and that's unset if the SIS FB is not built in. It must check CONFIG_FB_SIS_MODULE as well. Signed-off-by: David Howells <dhowells@redhat.com> Cc: Dave Airlie <airlied@linux.ie> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Dave Airlie <airlied@redhat.com>		2008-10-18 07:10:09 +10:00
..
i810
i830
i915	misc: replace __FUNCTION__ with __func__	2008-10-16 11:21:30 -07:00
mga
r128
radeon	drm/radeon: downgrade debug message from info to debug.	2008-09-01 08:51:52 +10:00
savage
sis	SiS DRM: fix the memory allocator if the SIS FB is built as a module	2008-10-18 07:10:09 +10:00
tdfx
via
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_bufs.c
drm_context.c
drm_dma.c
drm_drawable.c
drm_drv.c	drm: make drm_minors_cleanup() static	2008-07-26 12:00:11 -07:00
drm_fops.c
drm_hashtab.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c	drm: don't call the vblank tasklet with irqs disabled.	2008-08-25 06:35:21 +10:00
drm_lock.c	drm: don't set the signal blocker on the master process.	2008-08-25 06:35:33 +10:00
drm_memory.c
drm_mm.c
drm_pci.c
drm_proc.c
drm_scatter.c
drm_sman.c
drm_stub.c
drm_sysfs.c
drm_vm.c
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