You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
kernel_samsung_sm7125/drivers/gpu/drm
Laurent Pinchart f41ced8f10 Check fops_get() return value 16 years ago
..
i810
i830
i915 drm/i915: fix modeset devname allocation + agp init return check. 16 years ago
mga
r128
radeon drm/radeon: use locked rmmap to remove sarea mapping. 16 years ago
savage
sis
tdfx
via
Kconfig drm: kconfig have drm core select i2c for kms 16 years ago
Makefile DRM: add mode setting support 16 years ago
README.drm
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_bufs.c drm/radeon: use locked rmmap to remove sarea mapping. 16 years ago
drm_cache.c
drm_context.c
drm_crtc.c drm: drop DRM_IOCTL_MODE_REPLACEFB, add+remove works just as well. 16 years ago
drm_crtc_helper.c drm: pin new and unpin old buffer when setting a mode. 16 years ago
drm_dma.c
drm_drawable.c
drm_drv.c drm: Avoid use-before-null-test on dev in drm_cleanup(). 16 years ago
drm_edid.c drm: fix useless gcc unused variable warning 16 years ago
drm_fops.c Check fops_get() return value 16 years ago
drm_gem.c drm: PAGE_CACHE_WC is x86 only so far 16 years ago
drm_hashtab.c drm: GEM mmap support 16 years ago
drm_ioc32.c
drm_ioctl.c
drm_irq.c drm: Add a debug node for vblank state. 16 years ago
drm_lock.c
drm_memory.c
drm_mm.c DRM: add mode setting support 16 years ago
drm_modes.c DRM: add mode setting support 16 years ago
drm_pci.c
drm_proc.c drm: Add a debug node for vblank state. 16 years ago
drm_scatter.c
drm_sman.c
drm_stub.c DRM: add mode setting support 16 years ago
drm_sysfs.c DRM: add mode setting support 16 years ago
drm_vm.c drm: GEM mmap support 16 years ago

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