summaryrefslogtreecommitdiff
path: root/Documentation/DocBook
diff options
context:
space:
mode:
authorMichael Witten <mfwitten@gmail.com>2011-08-25 19:41:37 +0000
committerMichael Witten <mfwitten@gmail.com>2011-08-29 19:59:59 +0000
commit54f2cb8fc930e08fd6156519b28c45d576615f82 (patch)
tree3d10a9759ebdb89b98da2f4be0518074e37d48cc /Documentation/DocBook
parent482b2ad8e488e609bb3bb408a8e9ca17b73b17c6 (diff)
DocBook/drm: Use a singular subject for grammatical cleanliness
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'Documentation/DocBook')
-rw-r--r--Documentation/DocBook/drm.tmpl8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index d385e902f5ff..3470c6b2f843 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -455,7 +455,7 @@
a GTT DRM MM object, which provides an address space pool for
object allocation. In a KMS configuration, the driver
needs to allocate and initialize a command ring buffer following
- core GEM initialization. Most UMA devices have a so-called
+ core GEM initialization. A UMA device usually has a so-called
"stolen" memory region, which provides space for the initial
framebuffer and large, contiguous memory regions required by the
device. This space is not typically managed by GEM, and must
@@ -635,10 +635,10 @@ void intel_crt_init(struct drm_device *dev)
a client calls the vblank wait ioctl above.
</para>
<para>
- Devices that don't provide a count register may simply use an
+ A device that doesn't provide a count register may simply use an
internal atomic counter incremented on every vertical blank
- interrupt, and can make their enable and disable vblank
- functions into no-ops.
+ interrupt (and then treat the enable_vblank() and disable_vblank()
+ callbacks as no-ops).
</para>
</sect1>