Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Drop trailing whitespace.

Browse Source
This commit is contained in:
wiz 2006-12-23 06:36:19 +00:00
parent 10058f19c8
commit fa9034328d
6 changed files with 29 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
share/man/man9/ddc.9
View File

@ -1,4 +1,4 @@
.\" $NetBSD: ddc.9,v 1.2 2006/12/03 05:28:33 tsutsui Exp $
.\" $NetBSD: ddc.9,v 1.3 2006/12/23 06:36:19 wiz Exp $
.\"
.\" Copyright 2006 Itronix Inc.
.\" All rights reserved.
@ -57,7 +57,7 @@ argument is a machine-dependent tag used to specify the I2C
bus on which the DDCv2 device is located.
The
.Fa dest
argument is a pointer to a buffer where the EDID data will be stored.
argument is a pointer to a buffer where the EDID data will be stored.
The
.Fa len
argument is the amount of data to read into the buffer. (The buffer must be
@ -65,7 +65,7 @@ large enough.) Typically, this value will be 128, which is the size of a
normal EDID data block.
.Pp
Normally the EDID data block will be post-processed with the
.Fn edid_parse
.Fn edid_parse
function.
.Sh RETURN VALUES
The

12
share/man/man9/edid.9
View File

@ -1,4 +1,4 @@
.\" $NetBSD: edid.9,v 1.1 2006/05/11 21:00:20 gdamore Exp $
.\" $NetBSD: edid.9,v 1.2 2006/12/23 06:36:19 wiz Exp $
.\"
.\" Copyright 2006 Itronix Inc.
.\" All rights reserved.
@ -58,7 +58,7 @@ which describes a display device such as a monitor or flat panel display.
.Pp
The
.Fn edid_is_valid
function simply tests if the EDID block in
function simply tests if the EDID block in
.Fa data
contains valid data. This test includes a verification of the checksum,
and that valid vendor and product idenfication data is present. The data
@ -74,7 +74,7 @@ data into the structure pointed to by
.Pp
The
.Fn edid_print
function prints the data in the given
function prints the data in the given
.Fa info
structure to the console device.
.Pp
@ -105,9 +105,9 @@ All pathnames are relative to
The EDID subsystem is implemented within the file
.Pa sys/dev/videomode/edid.c .
.Pp
The EDID subsystem also makes use of VESA Generalized Timing Formula located
located in
.Pa sys/dev/videomode/vesagtf.c
The EDID subsystem also makes use of VESA Generalized Timing Formula located
located in
.Pa sys/dev/videomode/vesagtf.c
and the generic videomode database located in
.Pa sys/dev/videomode/videomode.c .
.Sh EXAMPLES

4
share/man/man9/hashinit.9
View File

@ -1,4 +1,4 @@
.\" $NetBSD: hashinit.9,v 1.2 2006/06/05 16:48:35 chap Exp $
.\" $NetBSD: hashinit.9,v 1.3 2006/12/23 06:36:19 wiz Exp $
.\"
.\" Copyright (c) 2006 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -109,7 +109,7 @@ The value returned by
.Fn hashinit
should be cast as pointer to an array of
.Dv LIST_HEAD
or
or
.Dv TAILQ_HEAD
as appropriate.
It can be

14
share/man/man9/mutex.9
View File

@ -1,4 +1,4 @@
.\" $NetBSD: mutex.9,v 1.3 2006/11/14 15:30:09 ad Exp $
.\" $NetBSD: mutex.9,v 1.4 2006/12/23 06:36:19 wiz Exp $
.\"
.\" Copyright (c) 2006 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -43,7 +43,7 @@
.Nm mutex_destroy ,
.Nm mutex_enter ,
.Nm mutex_exit ,
.Nm mutex_tryenter
.Nm mutex_tryenter
.Nm mutex_owned
.Nd mutual exclusion primitives
.Sh SYNOPSIS
@ -73,7 +73,7 @@ same interface:
.It Dv MUTEX_ADAPTIVE
Adaptive mutexes provide mutual exclusion between LWPs.
.Pp
When initializing an adaptive mutex, IPL_NONE must be specified as the
When initializing an adaptive mutex, IPL_NONE must be specified as the
.Ar ipl
argument.
Adaptive mutexes can not be acquired from an interrupt handler.
@ -90,7 +90,7 @@ argument is used to pass an system interrupt priority level (SPL)
that will block all interrupt handlers that may try to acquire the mutex.
.Pp
LWPs that own spin mutexes may not sleep, and therefore must not
try to acquire adaptive mutexes or other sleep locks.
try to acquire adaptive mutexes or other sleep locks.
.Pp
A processor will always busy-wait when attempting to acquire
a spin mutex that is already held.
@ -104,7 +104,7 @@ The following types should be requested:
General mutex type.
May sleep.
.It Dv MUTEX_DRIVER
Device driver mutex.
Device driver mutex.
May or may not sleep.
.El
.Pp
@ -145,7 +145,7 @@ mutex is acquired.
.Pp
Mutexes and other types of locks must always be acquired in a
consistent order with respect to each other.
Otherwise, the potential for system deadlock exists.
Otherwise, the potential for system deadlock exists.
.It Fn mutex_exit "mtx"
.Pp
Release a mutex.
@ -179,7 +179,7 @@ source tree where code implementing mutexes can be found.
All pathnames are relative to
.Pa /usr/src .
.Pp
The core of the mutex implementation is in
The core of the mutex implementation is in
.Pa sys/kern/kern_mutex.c .
.Pp
The header file

18
share/man/man9/rwlock.9
View File

@ -1,4 +1,4 @@
.\" $NetBSD: rwlock.9,v 1.2 2006/11/13 18:28:15 ad Exp $
.\" $NetBSD: rwlock.9,v 1.3 2006/12/23 06:36:19 wiz Exp $
.\"
.\" Copyright (c) 2006 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -129,16 +129,16 @@ Release resources used by a lock.
The lock may not be used after it has been destroyed.
.It Fn rw_enter "rw" "op"
.Pp
If
If
.Dv RW_READER
is specified as the argument to
is specified as the argument to
.Fa op ,
acquire a read lock.
If the lock is write held, the caller will block and not return until the
hold is acquired.
Callers must not recursively acquire read locks.
.Pp
If
If
.Dv RW_WRITER
is specified, acquire a write lock.
If the lock is already held, the caller will block and not return until the
@ -146,7 +146,7 @@ hold is acquired.
.Pp
RW locks and other types of locks must always be acquired in a
consistent order with respect to each other.
Otherwise, the potential for system deadlock exists.
Otherwise, the potential for system deadlock exists.
.It Fn rw_exit "rw"
.Pp
Release a lock.
@ -157,9 +157,9 @@ Try to acquire a lock, but do not block if the lock is already held.
If the lock is acquired successfully, return non-zero.
Otherwise, return zero.
.Pp
Valid arguments to
Valid arguments to
.Fa op
are
are
.Dv RW_READ
or
.Dv RW_WRITE .
@ -175,7 +175,7 @@ Downgrade a lock from a write hold to a read hold.
.It Fn rw_read_held "rw"
.It Fn rw_lock_held "rw"
.Pp
Test the lock's condition and return non-zero if the lock is held
Test the lock's condition and return non-zero if the lock is held
(potentially by the current LWP) and matches the specified condition.
Otherwise, return zero.
.Pp
@ -189,7 +189,7 @@ source tree where code implementing RW locks can be found.
All pathnames are relative to
.Pa /usr/src .
.Pp
The core of the RW lock implementation is in
The core of the RW lock implementation is in
.Pa sys/kern/kern_rwlock.c .
.Pp
The header file

4
share/man/man9/scheduler.9
View File

@ -1,4 +1,4 @@
.\" $NetBSD: scheduler.9,v 1.4 2006/12/04 15:36:23 hubertf Exp $
.\" $NetBSD: scheduler.9,v 1.5 2006/12/23 06:36:19 wiz Exp $
.\"
.\" Copyright (c) 2002 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -69,7 +69,7 @@ The
.Nx
thread scheduling sub-system employs a
.Dq multilevel feedback queues
algorithm, favouring interactive, short-runnig threads to
algorithm, favouring interactive, short-runnig threads to
CPU-bound ones.
.Pp
.Fn resetpriority