kernel-fxtec-pro1x/drivers/gpu/drm
Jerome Glisse 771fe6b912 drm/radeon: introduce kernel modesetting for radeon hardware
Add kernel modesetting support to radeon driver, use the ttm memory
manager to manage memory and DRM/GEM to provide userspace API.
In order to avoid backward compatibility issue and to allow clean
design and code the radeon kernel modesetting use different code path
than old radeon/drm driver.

When kernel modesetting is enabled the IOCTL of radeon/drm
driver are considered as invalid and an error message is printed
in the log and they return failure.

KMS enabled userspace will use new API to talk with the radeon/drm
driver. The new API provide functions to create/destroy/share/mmap
buffer object which are then managed by the kernel memory manager
(here TTM). In order to submit command to the GPU the userspace
provide a buffer holding the command stream, along this buffer
userspace have to provide a list of buffer object used by the
command stream. The kernel radeon driver will then place buffer
in GPU accessible memory and will update command stream to reflect
the position of the different buffers.

The kernel will also perform security check on command stream
provided by the user, we want to catch and forbid any illegal use
of the GPU such as DMA into random system memory or into memory
not owned by the process supplying the command stream. This part
of the code is still incomplete and this why we propose that patch
as a staging driver addition, future security might forbid current
experimental userspace to run.

This code support the following hardware : R1XX,R2XX,R3XX,R4XX,R5XX
(radeon up to X1950). Works is underway to provide support for R6XX,
R7XX and newer hardware (radeon from HD2XXX to HD4XXX).

Authors:
    Jerome Glisse <jglisse@redhat.com>
    Dave Airlie <airlied@redhat.com>
    Alex Deucher <alexdeucher@gmail.com>

Signed-off-by: Jerome Glisse <jglisse@redhat.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2009-06-15 12:01:53 +10:00
..
i810 drm: Split drm_map and drm_local_map 2009-03-13 14:23:56 +10:00
i830 drm: Split drm_map and drm_local_map 2009-03-13 14:23:56 +10:00
i915 drm/i915: duplicate desired mode for use by fbcon. 2009-06-12 15:00:01 +10:00
mga drm: Make drm_local_map use a resource_size_t offset 2009-03-13 14:23:57 +10:00
r128 drm/r128: fix r128 ioremaps to use ioremap_wc. 2009-05-06 09:04:52 +10:00
radeon drm/radeon: introduce kernel modesetting for radeon hardware 2009-06-15 12:01:53 +10:00
savage drm: Use resource_size_t for drm_get_resource_{start, len} 2009-03-13 14:23:56 +10:00
sis SiS DRM: fix a pointer cast warning 2008-10-18 07:10:10 +10:00
tdfx
ttm drm: Add the TTM GPU memory manager subsystem. 2009-06-15 09:37:57 +10:00
via drm/via: vfree() no need checking before calling it 2009-06-12 14:59:59 +10:00
ati_pcigart.c drm/ati_pcigart: use memset_io to reset the memory 2009-03-13 14:24:14 +10:00
drm_agpsupport.c drm: stash AGP include under the do-we-have-AGP ifdef 2009-01-22 22:27:11 +10:00
drm_auth.c drm: move to kref per-master structures. 2008-12-29 17:47:22 +10:00
drm_bufs.c drm: don't associate _DRM_DRIVER maps with a master 2009-06-11 16:15:29 +10:00
drm_cache.c drm: wbinvd is cache coherent. 2008-10-18 07:10:53 +10:00
drm_context.c drm: Split drm_map and drm_local_map 2009-03-13 14:23:56 +10:00
drm_crtc.c drm: Release user fbs in drm_release 2009-02-20 12:21:11 +10:00
drm_crtc_helper.c drm/kms: don't try to shortcut drm mode set function 2009-04-24 14:47:00 +10:00
drm_debugfs.c drm: Convert proc files to seq_file and introduce debugfs 2009-03-27 15:12:00 -07:00
drm_dma.c
drm_drawable.c drm: Avoid oops in DRM_IOCTL_RM_DRAW if a bad handle is supplied. 2008-10-23 13:46:54 +10:00
drm_drv.c drm: Copy back ioctl data to userspace regardless of return code. 2009-05-20 11:41:41 -07:00
drm_edid.c drm: Eliminate magic I2C frobbing when reading EDID 2009-06-12 15:37:27 +10:00
drm_fops.c drm: drm_fops.c unlock missing on error path 2009-03-29 18:31:47 +10:00
drm_gem.c drm: simplify kcalloc() call to kzalloc(). 2009-06-11 16:10:30 +10:00
drm_hashtab.c drm: Export hash table functionality. 2009-06-12 15:56:33 +10:00
drm_info.c drm: merge Linux master into HEAD 2009-03-28 20:22:18 -04:00
drm_ioc32.c drm: Only use DRM_IOCTL_UPDATE_DRAW compat wrapper for compat X86. 2009-03-13 14:24:04 +10:00
drm_ioctl.c drm: fix leak of uninitialized data to userspace 2008-12-29 17:47:22 +10:00
drm_irq.c drm: Correct unbalanced drm_vblank_put() during mode setting. 2009-02-25 14:45:50 +10:00
drm_lock.c drm: Avoid client deadlocks when the master disappears. 2009-03-03 09:50:20 +10:00
drm_memory.c drm: Split drm_map and drm_local_map 2009-03-13 14:23:56 +10:00
drm_mm.c drm: Memory fragmentation from lost alignment blocks 2009-06-15 09:35:33 +10:00
drm_modes.c drm: Replace DRM_DEBUG with DRM_DEBUG_MODE in drm_mode 2009-06-12 14:59:42 +10:00
drm_pci.c
drm_proc.c drm: Convert proc files to seq_file and introduce debugfs 2009-03-27 15:12:00 -07:00
drm_scatter.c
drm_sman.c
drm_stub.c drm: add separate drm debugging levels 2009-06-11 18:36:36 +10:00
drm_sysfs.c drm: remove unreachable code in drm_sysfs.c 2009-04-24 15:06:36 +10:00
drm_vm.c drm: Make drm_local_map use a resource_size_t offset 2009-03-13 14:23:57 +10:00
Kconfig drm/radeon: introduce kernel modesetting for radeon hardware 2009-06-15 12:01:53 +10:00
Makefile drm: Add the TTM GPU memory manager subsystem. 2009-06-15 09:37:57 +10:00
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