summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorMichael Witten <mfwitten@gmail.com>2011-08-29 15:59:56 +0000
committerMichael Witten <mfwitten@gmail.com>2011-08-29 20:00:22 +0000
commit0c2d91a80a156208d2f9f3dfb01871ebcf4a9338 (patch)
treef21896e9252f291e5e4fed1b2440077473d59c8f /Documentation
parentf877bd4ad5508e2f0653c31d05ffe0ad4e2bfe11 (diff)
downloadop-kernel-dev-0c2d91a80a156208d2f9f3dfb01871ebcf4a9338.zip
op-kernel-dev-0c2d91a80a156208d2f9f3dfb01871ebcf4a9338.tar.gz
DocBook/drm: Use an <itemizelist> for fundamental GEM operations
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/DocBook/drm.tmpl10
1 files changed, 7 insertions, 3 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 0387970..c358367 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -709,9 +709,13 @@ void intel_crt_init(struct drm_device *dev)
read &amp; write, mapping, and domain ownership transfers.
</para>
<para>
- On a fundamental level, GEM involves several operations: memory
- allocation and freeing, command execution, and aperture management
- at command execution time. Buffer object allocation is relatively
+ On a fundamental level, GEM involves several operations:
+ <itemizedlist>
+ <listitem>Memory allocation and freeing</listitem>
+ <listitem>Command execution</listitem>
+ <listitem>Aperture management at command execution time</listitem>
+ </itemizedlist>
+ Buffer object allocation is relatively
straightforward and largely provided by Linux's shmem layer, which
provides memory to back each object. When mapped into the GTT
or used in a command buffer, the backing pages for an object are
OpenPOWER on IntegriCloud