Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 275221
b: refs/heads/master
c: 0c2d91a
h: refs/heads/master
i:
  275219: 8a791bb
v: v3
  • Loading branch information
Michael Witten committed Aug 29, 2011
1 parent d4a0f00 commit de1fa44
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 4 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: f877bd4ad5508e2f0653c31d05ffe0ad4e2bfe11
refs/heads/master: 0c2d91a80a156208d2f9f3dfb01871ebcf4a9338
10 changes: 7 additions & 3 deletions trunk/Documentation/DocBook/drm.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -709,9 +709,13 @@ void intel_crt_init(struct drm_device *dev)
read & 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
Expand Down

0 comments on commit de1fa44

Please sign in to comment.