From de1fa4419b00410c08370bef3ac13da00f7fdbb4 Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Mon, 29 Aug 2011 15:59:56 +0000 Subject: [PATCH] --- yaml --- r: 275221 b: refs/heads/master c: 0c2d91a80a156208d2f9f3dfb01871ebcf4a9338 h: refs/heads/master i: 275219: 8a791bb5613e2e76d6f5d89841e6d00a0f85c039 v: v3 --- [refs] | 2 +- trunk/Documentation/DocBook/drm.tmpl | 10 +++++++--- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index 8a42174b55f2..7f867b2c59d2 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: f877bd4ad5508e2f0653c31d05ffe0ad4e2bfe11 +refs/heads/master: 0c2d91a80a156208d2f9f3dfb01871ebcf4a9338 diff --git a/trunk/Documentation/DocBook/drm.tmpl b/trunk/Documentation/DocBook/drm.tmpl index 0387970234b3..c358367f9f85 100644 --- a/trunk/Documentation/DocBook/drm.tmpl +++ b/trunk/Documentation/DocBook/drm.tmpl @@ -709,9 +709,13 @@ void intel_crt_init(struct drm_device *dev) read & write, mapping, and domain ownership transfers. - 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: + + Memory allocation and freeing + Command execution + Aperture management at command execution time + + 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