aboutsummaryrefslogtreecommitdiff
path: root/Documentation/DocBook
diff options
context:
space:
mode:
authorMichael Witten <mfwitten@gmail.com>2011-08-25 19:21:17 +0000
committerMichael Witten <mfwitten@gmail.com>2011-08-29 19:59:54 +0000
commit049cc903e714a27805eae0c34a4c34902a385032 (patch)
tree671bf1f73329c70f362d69cd6744d47b4f24279e /Documentation/DocBook
parentae63d793a43888eeb1c16422252d987aa37ab96c (diff)
DocBook/drm: Streamline wording of GEM initialization
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'Documentation/DocBook')
-rw-r--r--Documentation/DocBook/drm.tmpl2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 6977cd91779..7c11d790f74 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -451,7 +451,7 @@
GEM is an alternative to TTM, designed specifically for UMA
devices. It has simpler initialization and execution requirements
than TTM, but has no VRAM management capability. Core GEM
- initialization is comprised of a basic drm_mm_init call to create
+ is initialized by calling drm_mm_init() to create
a GTT DRM MM object, which provides an address space pool for
object allocation. In a KMS configuration, the driver
needs to allocate and initialize a command ring buffer following