浏览代码

DocBook/drm: Use an <itemizelist> for fundamental GEM operations

Signed-off-by: Michael Witten <mfwitten@gmail.com>
Michael Witten 14 年之前
父节点
当前提交
0c2d91a80a
共有 1 个文件被更改,包括 7 次插入3 次删除
  1. 7 3
      Documentation/DocBook/drm.tmpl

+ 7 - 3
Documentation/DocBook/drm.tmpl

@@ -709,9 +709,13 @@ void intel_crt_init(struct drm_device *dev)
 	read &amp; write, mapping, and domain ownership transfers.
 	read &amp; write, mapping, and domain ownership transfers.
       </para>
       </para>
       <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
 	straightforward and largely provided by Linux's shmem layer, which
 	provides memory to back each object.  When mapped into the GTT
 	provides memory to back each object.  When mapped into the GTT
 	or used in a command buffer, the backing pages for an object are
 	or used in a command buffer, the backing pages for an object are