From eaf923db2451a8fa29df481381c0e538fc7d3ac4 Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Thu, 25 Aug 2011 19:49:10 +0000 Subject: [PATCH] --- yaml --- r: 275213 b: refs/heads/master c: 3bf7df615612671271512aada7d83285f3fa731b h: refs/heads/master i: 275211: 31970ebff35bfd79df3a01565bf8f3084085bd02 v: v3 --- [refs] | 2 +- trunk/Documentation/DocBook/drm.tmpl | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index 0135198aae8b..4bec42f10966 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 1dbd39c3ea3967c41a09e81c826499f7ae9c8180 +refs/heads/master: 3bf7df615612671271512aada7d83285f3fa731b diff --git a/trunk/Documentation/DocBook/drm.tmpl b/trunk/Documentation/DocBook/drm.tmpl index 15541b1fc052..c24f50ce7862 100644 --- a/trunk/Documentation/DocBook/drm.tmpl +++ b/trunk/Documentation/DocBook/drm.tmpl @@ -462,8 +462,7 @@ be initialized separately into its own DRM MM object. - Initialization is driver specific, and depends on - the architecture of the device. In the case of Intel + Initialization is driver specific. In the case of Intel integrated graphics chips like 965GM, GEM initialization can be done by calling the internal GEM init function, i915_gem_do_init(). Since the 965GM is a UMA device