Fix some spelling errors.
This commit is contained in:
parent
e8354668bd
commit
a04dd7481b
@ -29,7 +29,7 @@
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: security.7,v 1.1 1998/12/20 20:12:17 dillon Exp $
|
||||
.\" $Id: buf.9,v 1.1 1998/12/22 19:47:48 dillon Exp $
|
||||
.\"
|
||||
.Dd December 22, 1998
|
||||
.Dt BUF 9
|
||||
@ -60,7 +60,7 @@ valid and dirty bits (m->valid, m->dirty) for pages in DEV_BSIZE chunks. Thus
|
||||
a platform with a hardware page size of 4096 bytes has 8 valid and 8 dirty
|
||||
bits. These bits are generally set and cleared in groups based on the device
|
||||
block size of the device backing the page. Complete page's worth are often
|
||||
refered to using the VM_PAGE_BITS_ALL bitmask (i.e. 0xFF if the hardware page
|
||||
referred to using the VM_PAGE_BITS_ALL bitmask (i.e. 0xFF if the hardware page
|
||||
size is 4096).
|
||||
.Pp
|
||||
VM buffers also keep track of a byte-granular dirty range and valid range.
|
||||
|
@ -26,7 +26,7 @@
|
||||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id$
|
||||
.\" $Id: devclass.9,v 1.1 1998/09/03 21:52:05 dfr Exp $
|
||||
.\"
|
||||
.Dd June 16, 1998
|
||||
.Dt devclass 9
|
||||
@ -34,7 +34,7 @@
|
||||
.Sh NAME
|
||||
.Nm devclass
|
||||
.Nd object representing a class of devices
|
||||
.Sh SYNOPSYS
|
||||
.Sh SYNOPSIS
|
||||
.Dv typedef struct devclass *devclass_t;
|
||||
.Sh DESCRIPTION
|
||||
.Pp
|
||||
|
@ -26,7 +26,7 @@
|
||||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id$
|
||||
.\" $Id: device.9,v 1.1 1998/09/03 21:52:05 dfr Exp $
|
||||
.\"
|
||||
.Dd June 16, 1998
|
||||
.Dt device 9
|
||||
@ -34,7 +34,7 @@
|
||||
.Sh NAME
|
||||
.Nm device
|
||||
.Nd an abstract representation of a device
|
||||
.Sh SYNOPSYS
|
||||
.Sh SYNOPSIS
|
||||
.Dv typedef struct device *device_t;
|
||||
.Sh DESCRIPTION
|
||||
.Pp
|
||||
@ -47,7 +47,7 @@ and all other devices are created dynamically during
|
||||
autoconfiguration. Normally devices representing toplevel busses in
|
||||
the system (ISA, PCI etc.) will be attached directly to
|
||||
.Dv root_bus
|
||||
and other devices will be added as children of their relavent bus.
|
||||
and other devices will be added as children of their relevant bus.
|
||||
.Pp
|
||||
The devices in a system form a tree. All devices except
|
||||
.Dv root_bus
|
||||
|
@ -72,7 +72,7 @@ This read-only register reflects the inputs on the parallel port interface.
|
||||
.Bl -column "Bit" "Name" "Description" -compact
|
||||
.It Em Bit Ta Em Name Ta Em Description
|
||||
.It 7 Ta nBUSY Ta "inverted version of parallel port Busy signal"
|
||||
.It 6 Ta nACK Ta "version of parellel port nAck signal"
|
||||
.It 6 Ta nACK Ta "version of parallel port nAck signal"
|
||||
.It 5 Ta PERROR Ta "version of parallel port PERROR signal"
|
||||
.It 4 Ta SELECT Ta "version of parallel port Select signal"
|
||||
.It 3 Ta nFAULT Ta "version of parallel port nFault signal"
|
||||
@ -144,7 +144,7 @@ the current value of the internal
|
||||
This data is modified by some of the microinstructions, not all.
|
||||
.Ss MS_OP_GET and MS_OP_PUT
|
||||
are microinstructions used to do either predefined standard IEEE1284-1994
|
||||
transfers or programed non-standard io.
|
||||
transfers or programmed non-standard io.
|
||||
.Ss MS_OP_RFETCH - Register FETCH
|
||||
is used to retrieve the current value of a parallel port register, apply a
|
||||
mask and save it in a buffer.
|
||||
@ -261,7 +261,7 @@ integer return code
|
||||
.Pp
|
||||
Predefined macro: MS_RET(code)
|
||||
.Ss MS_OP_C_CALL - C function CALL
|
||||
is used to call C functions from microsequence execution. This may be usefull
|
||||
is used to call C functions from microsequence execution. This may be useful
|
||||
when a non-standard i/o is performed to retrieve a data character from the
|
||||
parallel port.
|
||||
.Pp
|
||||
@ -279,7 +279,7 @@ The ptr parameter is the current position in the buffer currently scanned.
|
||||
.Pp
|
||||
Predefined macro: MS_C_CALL(func,param)
|
||||
.Ss MS_OP_PTR - initialize internal PTR
|
||||
is used to initilize the internal pointeur to the currently scanned buffer.
|
||||
is used to initialize the internal pointer to the currently scanned buffer.
|
||||
This pointer is passed to any C call (see above).
|
||||
.Pp
|
||||
Parameter:
|
||||
@ -290,7 +290,7 @@ Note that this pointer is automatically incremented during xxx_P() calls
|
||||
.El
|
||||
.Pp
|
||||
Predefined macro: MS_PTR(ptr)
|
||||
.Ss MS_OP_ADELAY - do an Asynchroneous DELAY
|
||||
.Ss MS_OP_ADELAY - do an Asynchronous DELAY
|
||||
is used to make a tsleep() during microsequence execution. The tsleep is
|
||||
executed at PPBPRI level.
|
||||
.Pp
|
||||
@ -427,7 +427,7 @@ definition. For example,
|
||||
.Ed
|
||||
.Pp
|
||||
Here, some parameters are undefined and must be filled before executing
|
||||
the microsequence. In order to initialize seach a microsequence, one
|
||||
the microsequence. In order to initialize each microsequence, one
|
||||
should use the ppb_MS_init_msq() function like this:
|
||||
.Bd -literal
|
||||
ppb_MS_init_msq(select_microseq, 2,
|
||||
|
@ -23,7 +23,7 @@
|
||||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $Id: sleep.9,v 1.12 1998/12/21 10:34:53 dillon Exp $
|
||||
.\" $Id: sleep.9,v 1.13 1998/12/23 00:24:59 dillon Exp $
|
||||
.\" "
|
||||
.Dd December 17, 1998
|
||||
.Os
|
||||
@ -196,7 +196,7 @@ These routines may also be used to avoid nasty spl*() calls to get around
|
||||
race conditions with simple conditional test/wait interlocks. You simple
|
||||
call
|
||||
.Fn asleep
|
||||
prior to your test, then conditonally
|
||||
prior to your test, then conditionally
|
||||
.Fn await
|
||||
only if the test fails. It is usually a good idea to cancel an
|
||||
.Fn asleep
|
||||
|
Loading…
Reference in New Issue
Block a user