os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Spelling police.

Browse source
This commit is contained in:
Mike Pritchard 1996-12-28 23:36:54 +00:00
parent b64ff0c8f8
commit be87926aaf
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=911
27 changed files with 115 additions and 115 deletions
Download patch file Download diff file Expand all files Collapse all files

14
data/tutorials/ddwg/ddwg.sgml
View file

@ -6,7 +6,7 @@
++
++ Copyright Eric L. Hernes - Wednesday, August 2, 1995
++
++ $Id: ddwg.sgml,v 1.2 1996-10-06 20:17:08 jfieber Exp $
++ $Id: ddwg.sgml,v 1.3 1996-12-28 23:36:51 mpp Exp $
++
++ Sgml doc for something
-->
@ -20,8 +20,8 @@
<abstract>
This document describes how to add a device driver to FreeBSD. It is
<it/not/ intended to be a tutorial on unix device drivers in general.
It is intended for device driver authors, familiar with the unix
<it/not/ intended to be a tutorial on UNIX device drivers in general.
It is intended for device driver authors, familiar with the UNIX
device driver model, to work on FreeBSD.
</abstract>
@ -464,7 +464,7 @@ The steps required to add your driver to the standard FreeBSD kernel are
<p>
The standard model for adding a device driver to the Berkeley kernel
is to add your driver to the list of known devices. This list is
dependant on the cpu architecture. If the device is not i386 specific
dependent on the CPU architecture. If the device is not i386 specific
(PCCARD, PCI, SCSI), the file is in ``/usr/src/sys/conf/files''.
If the device is i386 specific, use ``/usr/src/sys/i386/conf/files.i386''.
A typical line looks like:
@ -793,9 +793,9 @@ Lines 132 - 139
driver, as opposed to an LKM filesystem, or an LKM system call.
<code>
132 /*
133 * this macro maps to a funtion which
133 * this macro maps to a function which
134 * sets the LKM up for a driver
135 * as opposed to a filesystem, systemcall, or misc
135 * as opposed to a filesystem, system call, or misc
136 * LKM.
137 */
138 MOD_DEV("pcaudio_mod", LM_DT_CHAR, 24, &amp;pcacdevsw);
@ -833,7 +833,7 @@ and just refer to the shared memory segment via pointers.
151 /*
152 * this maps the shared memory address
153 * from physical to virtual, to be
154 * consistant with the way
154 * consistent with the way
155 * /usr/src/sys/i386/isa.c handles it.
156 */
157 pcadev[i].id_maddr -=0xa0000;