diff options
author | Michael Witten <mfwitten@gmail.com> | 2011-08-25 15:41:37 -0400 |
---|---|---|
committer | Michael Witten <mfwitten@gmail.com> | 2011-08-29 15:59:59 -0400 |
commit | 54f2cb8fc930e08fd6156519b28c45d576615f82 (patch) | |
tree | 3d10a9759ebdb89b98da2f4be0518074e37d48cc /Documentation | |
parent | 482b2ad8e488e609bb3bb408a8e9ca17b73b17c6 (diff) |
DocBook/drm: Use a singular subject for grammatical cleanliness
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/DocBook/drm.tmpl | 8 |
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 @@ | |||
455 | a GTT DRM MM object, which provides an address space pool for | 455 | a GTT DRM MM object, which provides an address space pool for |
456 | object allocation. In a KMS configuration, the driver | 456 | object allocation. In a KMS configuration, the driver |
457 | needs to allocate and initialize a command ring buffer following | 457 | needs to allocate and initialize a command ring buffer following |
458 | core GEM initialization. Most UMA devices have a so-called | 458 | core GEM initialization. A UMA device usually has a so-called |
459 | "stolen" memory region, which provides space for the initial | 459 | "stolen" memory region, which provides space for the initial |
460 | framebuffer and large, contiguous memory regions required by the | 460 | framebuffer and large, contiguous memory regions required by the |
461 | device. This space is not typically managed by GEM, and must | 461 | device. This space is not typically managed by GEM, and must |
@@ -635,10 +635,10 @@ void intel_crt_init(struct drm_device *dev) | |||
635 | a client calls the vblank wait ioctl above. | 635 | a client calls the vblank wait ioctl above. |
636 | </para> | 636 | </para> |
637 | <para> | 637 | <para> |
638 | Devices that don't provide a count register may simply use an | 638 | A device that doesn't provide a count register may simply use an |
639 | internal atomic counter incremented on every vertical blank | 639 | internal atomic counter incremented on every vertical blank |
640 | interrupt, and can make their enable and disable vblank | 640 | interrupt (and then treat the enable_vblank() and disable_vblank() |
641 | functions into no-ops. | 641 | callbacks as no-ops). |
642 | </para> | 642 | </para> |
643 | </sect1> | 643 | </sect1> |
644 | 644 | ||