Documentation: fix typos in drm docbook

Fix spelling typo in DocBook/drm.tmpl

Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Dave Airlie <airlied@redhat.com>
This commit is contained in:
Masanari Iida 2014-05-15 13:54:06 -07:00 committed by Dave Airlie
parent b5e6c1dace
commit 9a6594fc52
1 changed files with 6 additions and 6 deletions

View File

@ -79,7 +79,7 @@
<partintro> <partintro>
<para> <para>
This first part of the DRM Developer's Guide documents core DRM code, This first part of the DRM Developer's Guide documents core DRM code,
helper libraries for writting drivers and generic userspace interfaces helper libraries for writing drivers and generic userspace interfaces
exposed by DRM drivers. exposed by DRM drivers.
</para> </para>
</partintro> </partintro>
@ -451,7 +451,7 @@ char *date;</synopsis>
providing a solution to every graphics memory-related problems, GEM providing a solution to every graphics memory-related problems, GEM
identified common code between drivers and created a support library to identified common code between drivers and created a support library to
share it. GEM has simpler initialization and execution requirements than share it. GEM has simpler initialization and execution requirements than
TTM, but has no video RAM management capabitilies and is thus limited to TTM, but has no video RAM management capabilities and is thus limited to
UMA devices. UMA devices.
</para> </para>
<sect2> <sect2>
@ -881,7 +881,7 @@ int (*prime_fd_to_handle)(struct drm_device *dev,
vice versa. Drivers must use the kernel dma-buf buffer sharing framework vice versa. Drivers must use the kernel dma-buf buffer sharing framework
to manage the PRIME file descriptors. Similar to the mode setting to manage the PRIME file descriptors. Similar to the mode setting
API PRIME is agnostic to the underlying buffer object manager, as API PRIME is agnostic to the underlying buffer object manager, as
long as handles are 32bit unsinged integers. long as handles are 32bit unsigned integers.
</para> </para>
<para> <para>
While non-GEM drivers must implement the operations themselves, GEM While non-GEM drivers must implement the operations themselves, GEM
@ -2348,7 +2348,7 @@ void intel_crt_init(struct drm_device *dev)
first create properties and then create and associate individual instances first create properties and then create and associate individual instances
of those properties to objects. A property can be instantiated multiple of those properties to objects. A property can be instantiated multiple
times and associated with different objects. Values are stored in property times and associated with different objects. Values are stored in property
instances, and all other property information are stored in the propery instances, and all other property information are stored in the property
and shared between all instances of the property. and shared between all instances of the property.
</para> </para>
<para> <para>
@ -2689,10 +2689,10 @@ int num_ioctls;</synopsis>
<sect1> <sect1>
<title>Legacy Support Code</title> <title>Legacy Support Code</title>
<para> <para>
The section very brievely covers some of the old legacy support code which The section very briefly covers some of the old legacy support code which
is only used by old DRM drivers which have done a so-called shadow-attach is only used by old DRM drivers which have done a so-called shadow-attach
to the underlying device instead of registering as a real driver. This to the underlying device instead of registering as a real driver. This
also includes some of the old generic buffer mangement and command also includes some of the old generic buffer management and command
submission code. Do not use any of this in new and modern drivers. submission code. Do not use any of this in new and modern drivers.
</para> </para>