Direct Rendering Manager

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Direct Rendering Manager
Original author(s) kernel.org, freedesktop.org, et al.
Written in C
Type
License GNU General Public License
Website dri.freedesktop.org/wiki/DRM

The Direct Rendering Manager (DRM) is a device-independent kernel-level device driver that provides support for the Direct Rendering Infrastructure.[1] The Direct Rendering Manager can be compiled into the Linux kernel or loaded via the standard module interface.

Software architecture[edit]

  • The DRM provides synchronized access to the graphics hardware via the use of an optimized two-tiered lock.
  • 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.
  • The DRM provides a generic DMA engine, complete with multiple queues and the ability to detect the need for an OpenGL context switch.
  • The DRM is extensible via the use of small device-specific modules that rely extensively on the API exported by the DRM module.

It consists of two in-kernel drivers: a generic drm driver, and another which has specific support for the GPUs. This pair of drivers allows a userspace client direct access to the video hardware. The entire DRI system enables hardware accelerated 3D rendering, video decoding as well as GPGPU.

AGP, PCIe and other graphics cards contain an IOMMU called Graphics address remapping table (GART) which can be used to map various pages of system memory into the GPU's address space. The result is that, at any time, an arbitrary (scattered) subset of the system's RAM pages are accessible to the GPU.[2]

Linux kernel version 3.11, which was released on 2013-09-02, included major changes to the direct rendering manager.[3]

API[edit]

The DRM core exports several interfaces to user-space applications, generally intended to be used through corresponding libdrm wrapper functions. In addition, drivers export device-specific interfaces for use by user-space drivers & device-aware applications through ioctls and sysfs files. External interfaces include: memory mapping, context management, DMA operations, AGP management, vblank control, fence management, memory management, and output management.

KMS driver (Kernel mode setting)[edit]

The KMS driver is the component which is solely responsible for the mode setting. It is the device driver for a display controller, and it can be distinguished from the device driver of a rendering accelerator. Due to the fact that dies of modern the GPU found on graphics cards for desktop computers integrate "processing logic", "display controller" and "hardware video acceleration" SIP cores, non-technical people don't distinguish between these three very different components. SoCs on the other hand, regularly mix SIP from different developers, and e.g. ARM's Mali SIP does not feature a display controller. For historical reasons, the DRM and the KMS of the Linux kernel were amalgamated into one component. They were split in 2013 for technical reasons.[4]

The video Embedded Linux Conference 2013 – Anatomy of an Embedded KMS driver on YouTube explains what a KMS driver is.

DRM/i915 obtained support for MIPI Display Serial Interface (DSI) for Linux kernel 3.16.[5]

Multi-monitor[edit]

Support for a multi-monitor set-up is of course an ability of the display controller. For example, AMD's display controllers since the Radeon HD 5000 Series, are advertised with the brand "AMD Eyefinity". This new capability of the hardware is supported by AMD's proprietary driver. Whether it is also supported by the KMS driver, this section will tell soon.

Render nodes[edit]

In version 3.12 an (experimental) implementation of render nodes were merged into the Direct Rendering Manager.[6][7][8][9]

A render node is a character device that exposes a GPU's off-screen rendering and GPGPU capabilities to unprivileged programs, without exposing any display manipulation access. This is the first step in of an effort to decouple the kernel's interfaces for GPUs and display controllers from the obsolete notion of a graphics card.[4] Coincidentally, unprivileged off-screen rendering is presumed by both Wayland and Mir display protocols — only the compositor is entitled to send its output to a display, and rendering on behalf of client programs is outside the scope of these protocols.

Universal plane[edit]

Patches for universal plane were submitted by Intel's Matthew. D. Roper in May 2014. The idea behind universal plane is to expose all types of hardware planes to userspace via one consistent Kernel–user space API.[10] Universal plane brings framebuffers (primary planes), overlays (secondary planes) and cursors (cursor planes) together under the same API. No more type specific ioctls, but common ioctls shared by them all. [11]

Universal plane prepares the way for Atomic mode setting and nuclear pageflip.

Hardware support[edit]

All hardware mentioned in the article free and open-source graphics device driver has drm code.[12]

As of August 2013, the kernel component of the freedreno driver mainly authored by Rob Clark for Qualcomm's Adreno GPU family, called MSM driver, has been accepted into mainline, and has been available since Linux kernel 3.12.[13][14]

In Linux kernel 3.13

  • DRM support for Marvell's ARMADA 510 display subsystem.[15]

See also[edit]

References[edit]

External links[edit]