linux/drivers/gpu/drm
Jesse Barnes 4a9216453c drm: when queuing an event with NEXTONMISS, return queued sequence to userspace
If we queue a vblank event but miss it, we should return the actual
sequence number we queued to userspace, so its event handling function
will know which event to look for.

Acked-by: Kristian Høgsberg <krh@bitplanet.net>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2009-11-18 10:02:48 +10:00
..
i810
i830
i915 drm: Add async event synchronization for drmWaitVblank 2009-11-18 10:02:47 +10:00
mga
r128
radeon drm/radeon/kms: ignore vga arbiter return. 2009-10-28 11:09:58 +10:00
savage
sis
tdfx
ttm Merge branch 'drm-next' of ../drm-next into drm-linus 2009-10-08 14:03:05 +10:00
via
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_bufs.c
drm_cache.c
drm_context.c
drm_crtc_helper.c drm/kms: protect against fb helper not being created. 2009-09-26 06:39:00 +10:00
drm_crtc.c drm: Delete the DRM_DEBUG_KMS in drm_mode_cursor_ioctl 2009-10-05 10:00:57 +10:00
drm_debugfs.c
drm_dma.c
drm_drawable.c
drm_drv.c
drm_edid.c drm: Add the basic check for the detailed timing in EDID 2009-10-28 11:23:39 +10:00
drm_encoder_slave.c
drm_fb_helper.c drm/kms: fix kms/fbdev colormap support properly. 2009-10-28 11:23:48 +10:00
drm_fops.c drm: Add async event synchronization for drmWaitVblank 2009-11-18 10:02:47 +10:00
drm_gem.c
drm_hashtab.c
drm_info.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c drm: when queuing an event with NEXTONMISS, return queued sequence to userspace 2009-11-18 10:02:48 +10:00
drm_lock.c
drm_memory.c
drm_mm.c
drm_modes.c drm/kms: start adding command line interface using fb. 2009-09-25 13:08:20 +10:00
drm_pci.c
drm_proc.c
drm_scatter.c
drm_sman.c
drm_stub.c drm: Add async event synchronization for drmWaitVblank 2009-11-18 10:02:47 +10:00
drm_sysfs.c
drm_vm.c const: mark struct vm_struct_operations 2009-09-27 11:39:25 -07:00
Kconfig
Makefile
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