From 41087c2687c8679db806b866d3181802912a035c Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Thu, 25 Aug 2011 18:46:10 +0000 Subject: [PATCH] --- yaml --- r: 275197 b: refs/heads/master c: 8814630f0b59421e558f4403b79f5dc3a025a386 h: refs/heads/master i: 275195: 23534e6846965bd4b8ba8e896bfc5a423fb968ca v: v3 --- [refs] | 2 +- trunk/Documentation/DocBook/drm.tmpl | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index 9d137222cac2..570e056489c6 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 57a15fd663d6680dc100a537f0ed328993c33af2 +refs/heads/master: 8814630f0b59421e558f4403b79f5dc3a025a386 diff --git a/trunk/Documentation/DocBook/drm.tmpl b/trunk/Documentation/DocBook/drm.tmpl index 33290e3e3ffa..25e0f460a973 100644 --- a/trunk/Documentation/DocBook/drm.tmpl +++ b/trunk/Documentation/DocBook/drm.tmpl @@ -321,10 +321,10 @@ Finding & mapping resources is fairly straightforward. The DRM wrapper functions, drm_get_resource_start() and - drm_get_resource_len() may be used to find BARs on the given + drm_get_resource_len(), may be used to find BARs on the given drm_device struct. Once those values have been retrieved, the driver load function can call drm_addmap() to create a new - mapping for the BAR in question. Note you probably want a + mapping for the BAR in question. Note that you probably want a drm_local_map_t in your driver private structure to track any mappings you create.