diff options
| author | Michael Witten <mfwitten@gmail.com> | 2011-08-25 21:37:24 +0200 |
|---|---|---|
| committer | Michael Witten <mfwitten@gmail.com> | 2011-08-29 21:59:56 +0200 |
| commit | 482b2ad8e488e609bb3bb408a8e9ca17b73b17c6 (patch) | |
| tree | 3b457e7ac118427d6f5de08b3803be64bb142f26 /Documentation/DocBook | |
| parent | DocBook/drm: Streamline wording of GEM initialization (diff) | |
| download | linux-482b2ad8e488e609bb3bb408a8e9ca17b73b17c6.tar.xz linux-482b2ad8e488e609bb3bb408a8e9ca17b73b17c6.zip | |
DocBook/drm: basic -> core
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'Documentation/DocBook')
| -rw-r--r-- | Documentation/DocBook/drm.tmpl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl index 7c11d790f749..d385e902f5ff 100644 --- a/Documentation/DocBook/drm.tmpl +++ b/Documentation/DocBook/drm.tmpl @@ -455,7 +455,7 @@ 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 - basic GEM initialization. Most UMA devices have a so-called + core GEM initialization. Most UMA devices have a so-called "stolen" memory region, which provides space for the initial framebuffer and large, contiguous memory regions required by the device. This space is not typically managed by GEM, and must |