Prepare for mdoc(7)NG.
This commit is contained in:
parent
9431f1fc08
commit
e207e465df
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=71101
@ -49,7 +49,7 @@ The
|
||||
node type performs encapsulation, de-encapsulation, and multiplexing
|
||||
of packets using the frame relay protocol. It supports up to 1024 DLCI's.
|
||||
The LMI protocol is handled by a separate node type (see
|
||||
.Xr ng_lmi 4 ).
|
||||
.Xr ng_lmi 4 ) .
|
||||
.Pp
|
||||
The
|
||||
.Dv downstream
|
||||
|
@ -335,7 +335,7 @@ the job at adapter level.
|
||||
A microsequence is an array of opcodes and parameters.
|
||||
Each opcode codes an
|
||||
operation (opcodes are described in
|
||||
.Xr microseq 9 ).
|
||||
.Xr microseq 9 ) .
|
||||
Standard I/O operations are implemented at ppbus level whereas basic I/O
|
||||
operations and microseq language are coded at adapter level for efficiency.
|
||||
.Pp
|
||||
|
@ -48,7 +48,7 @@ The
|
||||
is a two-wire interface through which simple power-related chips can communicate
|
||||
with rest of the system.
|
||||
It uses I2C as its backbone (see
|
||||
.Xr iicbus 4 ).
|
||||
.Xr iicbus 4 ) .
|
||||
.Pp
|
||||
A system using SMB passes messages to and from devices instead of tripping
|
||||
individual control lines.
|
||||
|
@ -158,7 +158,7 @@ The
|
||||
.Dv TCP_NOPUSH
|
||||
option is provided to allow servers to easily make use of Transaction
|
||||
TCP (see
|
||||
.Xr ttcp 4 ).
|
||||
.Xr ttcp 4 ) .
|
||||
When the option is set to a non-zero value,
|
||||
.Tn TCP
|
||||
will delay sending any data at all until either the socket is closed,
|
||||
|
@ -51,7 +51,7 @@ When a user logs into
|
||||
the system on one of these hardware terminal ports, the system has already
|
||||
opened the associated device and prepared the line for normal interactive
|
||||
use (see
|
||||
.Xr getty 8 .)
|
||||
.Xr getty 8 . )
|
||||
There is also a special case of a terminal file that connects not to
|
||||
a hardware terminal port, but to another program on the other side.
|
||||
These special terminal devices are called
|
||||
@ -69,7 +69,7 @@ how these lines are opened or used. Also, these lines are often used
|
||||
for dialing out of a system (through an out-calling modem), but again
|
||||
the system provides programs that hide the details of accessing
|
||||
these terminal special files (see
|
||||
.Xr tip 1 ).
|
||||
.Xr tip 1 ) .
|
||||
.Pp
|
||||
When an interactive user logs in, the system prepares the line to
|
||||
behave in a certain way (called a
|
||||
@ -97,7 +97,7 @@ essentially glues the low level device driver code with the high
|
||||
level generic interface routines (such as
|
||||
.Xr read 2
|
||||
and
|
||||
.Xr write 2 ),
|
||||
.Xr write 2 ) ,
|
||||
and is responsible for implementing the semantics associated
|
||||
with the device. When a terminal file is first opened by a program,
|
||||
the default
|
||||
|
@ -50,7 +50,7 @@ driver has three layers: the controller, the bus, and the
|
||||
device layer.
|
||||
The controller attaches to a physical bus
|
||||
(like
|
||||
.Xr pci 4 ).
|
||||
.Xr pci 4 ) .
|
||||
The
|
||||
.Tn USB
|
||||
bus attaches to the controller and the root hub attaches
|
||||
|
@ -73,7 +73,7 @@ and without the
|
||||
prefix,
|
||||
in which case that signal is delivered to the process
|
||||
(see
|
||||
.Xr sigaction 2 ).
|
||||
.Xr sigaction 2 ) .
|
||||
.It Pa dbregs
|
||||
The debug registers as defined by
|
||||
.Dv "struct dbregs"
|
||||
@ -190,7 +190,7 @@ file.
|
||||
The child process will receive a
|
||||
.Dv SIGTRAP
|
||||
immediately after the call to exec (see
|
||||
.Xr execve 2 ).
|
||||
.Xr execve 2 ) .
|
||||
.Pp
|
||||
Each node is owned by the process's user, and belongs to that user's
|
||||
primary group, except for the
|
||||
|
@ -639,7 +639,7 @@ is set to
|
||||
and is used for both
|
||||
.Xr kerberos 1
|
||||
and
|
||||
.Xr kadmind 8 ).
|
||||
.Xr kadmind 8 ) .
|
||||
.It Ar rwhod_enable
|
||||
(bool) If set to
|
||||
.Ar YES ,
|
||||
|
@ -53,14 +53,14 @@ The devices in a system form a tree.
|
||||
All devices except
|
||||
.Dv root_bus
|
||||
have a parent (see
|
||||
.Xr device_get_parent 9 ).
|
||||
.Xr device_get_parent 9 ) .
|
||||
In addition, any device can have children attached to it (see
|
||||
.Xr device_add_child 9 ,
|
||||
.Xr device_add_child_ordered 9 ,
|
||||
.Xr device_find_child 9 ,
|
||||
.Xr device_get_children 9 ,
|
||||
and
|
||||
.Xr device_delete_child 9 ).
|
||||
.Xr device_delete_child 9 ) .
|
||||
.Pp
|
||||
A device which has been successfully probed and attached to the
|
||||
system will also have a driver (see
|
||||
@ -70,17 +70,17 @@ and
|
||||
and a devclass (see
|
||||
.Xr device_get_devclass 9
|
||||
and
|
||||
.Xr devclass 9 ).
|
||||
.Xr devclass 9 ) .
|
||||
Various other attributes of the device include a unit number (see
|
||||
.Xr device_get_unit 9 ),
|
||||
.Xr device_get_unit 9 ) ,
|
||||
verbose description (normally supplied by the driver, see
|
||||
.Xr device_set_desc 9
|
||||
and
|
||||
.Xr device_get_desc 9 ),
|
||||
.Xr device_get_desc 9 ) ,
|
||||
a set of bus-specific variables (see
|
||||
.Xr device_get_ivars 9 )
|
||||
and a set of driver-specific variables (see
|
||||
.Xr device_get_softc 9 ).
|
||||
.Xr device_get_softc 9 ) .
|
||||
.Pp
|
||||
Devices can be in one of several states:
|
||||
.Bl -tag -width DS_NOTPRESENT
|
||||
|
@ -47,7 +47,7 @@ and deleted.
|
||||
If the device is currently attached, it is first detached (see
|
||||
.Xr DEVICE_ATTACH 9
|
||||
and
|
||||
.Xr DEVICE_DETACH 9 ).
|
||||
.Xr DEVICE_DETACH 9 ) .
|
||||
.Sh RETURN VALUES
|
||||
Zero is returned on success, otherwise an error is returned.
|
||||
.Sh SEE ALSO
|
||||
|
@ -59,7 +59,7 @@ which returns
|
||||
or
|
||||
.Dv DS_BUSY
|
||||
(described in
|
||||
.Xr device 9 ).
|
||||
.Xr device 9 ) .
|
||||
To test see if a device was successfully probed, call
|
||||
.Xr device_is_alive 9
|
||||
which simply returns if the state is greater or equal to
|
||||
|
@ -117,13 +117,13 @@ If you get a lock, remember to release the lock (using
|
||||
or
|
||||
.Xr VOP_UNLOCK 9
|
||||
and
|
||||
.Xr vrele 9 .)
|
||||
.Xr vrele 9 . )
|
||||
.It Dv WANTPARENT
|
||||
Make
|
||||
.Fn namei
|
||||
also return the parent (directory) vnode, in unlocked
|
||||
state. Remember to release it (using
|
||||
.Xr vrele 9 .)
|
||||
.Xr vrele 9 . )
|
||||
.It Dv NOCACHE
|
||||
Avoid
|
||||
.Fn namei
|
||||
|
@ -92,7 +92,7 @@ from
|
||||
.Va time
|
||||
at boot, and is updated by the periodic timer interrupt. (It is
|
||||
not updated by
|
||||
.Xr settimeofday 2 .)
|
||||
.Xr settimeofday 2 . )
|
||||
.Pp
|
||||
All of these variables contain times
|
||||
expressed in seconds and microseconds since midnight (0 hour),
|
||||
|
Loading…
Reference in New Issue
Block a user