Ispell sweep of share/man/man4.
This commit is contained in:
Mike Pritchard
parent
51d31ec2d8
commit
f87717fa8b
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=89610
@ -231,7 +231,7 @@ SCB space to be augmented with external SRAM up to a maximum of 255 SCBs.
|
||||
Very few Adaptec controller configurations have external SRAM.
|
||||
.Pp
|
||||
If external SRAM is not available, SCBs are a limited resource.
|
||||
Using the SCBs in a straight forward manner would only allow the dirver to
|
||||
Using the SCBs in a straight forward manner would only allow the driver to
|
||||
handle as many concurrent transactions as there are physical SCBs.
|
||||
To fully utilize the SCSI bus and the devices on it,
|
||||
requires much more concurrency.
|
||||
|
||||
@ -126,7 +126,7 @@ The following kernel configuration options control the
|
||||
driver.
|
||||
.Bl -tag -width ATKBD_DFLT
|
||||
.It Em ATKBD_DFLT_KEYMAP
|
||||
This option sets the defauilt, built-in keymap of the
|
||||
This option sets the default, built-in keymap of the
|
||||
.Nm
|
||||
driver to the named keymap.
|
||||
See
|
||||
|
||||
@ -77,7 +77,7 @@ Note however the device only supports a single
|
||||
speed in TBI mode.
|
||||
.Pp
|
||||
Most cards also use the Broadcom BCM5401 or BCM5411 10/100/1000
|
||||
copper gigabit tranceivers,
|
||||
copper gigabit transceivers,
|
||||
which support autonegotiation of 10, 100 and 1000mbps modes in
|
||||
full or half duplex.
|
||||
.Pp
|
||||
|
||||
@ -375,9 +375,9 @@ changer at the same time.
|
||||
The scheduler honors minimum and maximum time
|
||||
quanta that the driver will spend on a particular LUN. The minimum time
|
||||
is the guaranteed minimum amount of time that the driver will spend on a
|
||||
given LUN, even if there is no oustanding I/O for that LUN. The maximum
|
||||
given LUN, even if there is no outstanding I/O for that LUN. The maximum
|
||||
time is the maximum amount of time the changer will spend on a LUN if there
|
||||
is oustdanding I/O for another LUN. If there is no outstanding I/O for
|
||||
is outstanding I/O for another LUN. If there is no outstanding I/O for
|
||||
another LUN, the driver will allow indefinite access to a given LUN.
|
||||
.Pp
|
||||
The minimum and maximum time quanta are configurable via kernel options and
|
||||
@ -435,7 +435,7 @@ There is no mechanism currently to set different minimum and maximum
|
||||
timeouts for different CD changers; the timeout values set by the kernel
|
||||
options or the sysctl variables apply to all LUN-based CD changers in the
|
||||
system. It is possible to implement such support, but the sysctl
|
||||
impelmentation at least would be rather inelegant, because of the current
|
||||
implementation at least would be rather inelegant, because of the current
|
||||
inability of the sysctl code to handle the addition of nodes after compile
|
||||
time. Thus, it would take one dynamically sized sysctl variable and a
|
||||
userland utility to get/set the timeout values. Implementation of separate
|
||||
|
||||
@ -41,7 +41,7 @@ driver provides support for a
|
||||
media changer.
|
||||
It allows many slots of media to be multiplexed between
|
||||
a number of drives. The changer device may optionally be equipped
|
||||
with a bar code reader, which reads label informationen attached to
|
||||
with a bar code reader, which reads label information attached to
|
||||
the media.
|
||||
.Pp
|
||||
A SCSI adapter must also be separately configured into the system
|
||||
@ -76,7 +76,7 @@ has included the driver).
|
||||
.Sh IOCTLS
|
||||
User mode programs communicate with the changer driver through a
|
||||
number of ioctls which are described below. Changer element addresses
|
||||
used in the communcation between the kernel and the changer device are
|
||||
used in the communication between the kernel and the changer device are
|
||||
mapped to zero-based logical addresses. Element types are specified
|
||||
as follows:
|
||||
.Bl -tag -width CHET_MT
|
||||
@ -233,7 +233,7 @@ changer_voltag_t ces_avoltag; /* alternate volume tag */
|
||||
u_char ces_idvalid; /* ces_scsi_id is valid */
|
||||
u_char ces_scsi_id; /* SCSI id of element (if ces_idvalid is nonzero) */
|
||||
u_char ces_lunvalid; /* ces_scsi_lun is valid */
|
||||
u_char ces_scsi_lun; /* SCSI lun of elemtne (if ces_lunvalid is nonzero) */
|
||||
u_char ces_scsi_lun; /* SCSI lun of element (if ces_lunvalid is nonzero) */
|
||||
.Ed
|
||||
.Pp
|
||||
The ces_addr field contains the address of the element in the
|
||||
@ -267,7 +267,7 @@ and a Breece Hill Q47 (60 slot, four DLT drives, barcode reader).
|
||||
.Pp
|
||||
Many of the features the
|
||||
.Nm
|
||||
driver supports are not thouroghly tested due to the fact that the
|
||||
driver supports are not throughly tested due to the fact that the
|
||||
devices available for testing do not support the necessary commands.
|
||||
This is true for alternate volume tags, media flipping, import/export
|
||||
element handling, multiple picker operation and other things.
|
||||
|
||||
@ -136,7 +136,7 @@ remapping features are 'Auto Write Reallocation' and 'Auto Read
|
||||
Reallocation' which can be enabled via the AWRE and ARRE bits,
|
||||
respectively, of the Read-Write Error Recovery page.
|
||||
Many devices do not ship from the factory with these feature enabled.
|
||||
Mode pages can be examined and modifie
|
||||
Mode pages can be examined and modified
|
||||
via the
|
||||
.Xr camcontrol 8
|
||||
utility.
|
||||
|
||||
@ -92,7 +92,7 @@ peculiar bugs.
|
||||
The
|
||||
.Nm
|
||||
driver does its best to provide generalized support for all
|
||||
of these chipsets in order to keep special case code to a minimun.
|
||||
of these chipsets in order to keep special case code to a minimum.
|
||||
.Pp
|
||||
These chips are used by many vendors which makes it
|
||||
difficult to provide a complete list of all supported cards.
|
||||
@ -360,7 +360,7 @@ queues a sequence of frames which cause it to wrap from the end of the
|
||||
transmit descriptor ring back to the beginning.
|
||||
The
|
||||
.Nm
|
||||
driver attempts to avoid this condition by not queing any frames past
|
||||
driver attempts to avoid this condition by not queuing any frames past
|
||||
the end of the transmit ring during a single invocation of the
|
||||
.Fn dc_start
|
||||
routine.
|
||||
|
||||
@ -451,7 +451,7 @@ occurs. The
|
||||
argument defaults to 4.
|
||||
.Pp
|
||||
.Sy Warning :
|
||||
The hardware debug facilities do not have a concept of seperate
|
||||
The hardware debug facilities do not have a concept of separate
|
||||
address spaces like the watch command does. Use
|
||||
.Cm hwatch
|
||||
for setting watchpoints on kernel address locations only, and avoid
|
||||
|
||||
@ -44,7 +44,7 @@ To allow PCI adapters to use memory mapped I/O if enabled:
|
||||
The
|
||||
.Nm
|
||||
driver provides support for the DPT Smart Cache Plus, Smart Cache III,
|
||||
Smart Raid III, Smart Cache IV, and Smart RAID IV families of procucts.
|
||||
Smart Raid III, Smart Cache IV, and Smart RAID IV families of products.
|
||||
.Sh FILES
|
||||
.Bl -tag -width /usr/share/man0/template.doc -compact
|
||||
.It Pa sys/dev/dpt/dpt_scsi.c
|
||||
|
||||
@ -193,7 +193,7 @@ or any of the following
|
||||
.Xr ioctl 2
|
||||
commands.
|
||||
.Pp
|
||||
Whe opening the device with
|
||||
When opening the device with
|
||||
.Dv O_NONBLOCK
|
||||
set, automatic media density selection will be bypassed, and the device
|
||||
remains in a half-opened state.
|
||||
@ -266,7 +266,7 @@ The caller is assumed to use
|
||||
.Dv FD_GSTAT
|
||||
calls in order to inquire about the success of each operation.
|
||||
This
|
||||
is intented to allow even erroneous data from bad blocks to be
|
||||
is intended to allow even erroneous data from bad blocks to be
|
||||
retrieved using normal I/O operations.
|
||||
.It Dv FDOPT_AUTOSEL
|
||||
Device performs automatic density selection.
|
||||
|
||||
@ -34,7 +34,7 @@ interrupt than the one specified in the kernel configuration file.
|
||||
.It "fea%d: error: memory not enabled! ECU reconfiguration required"
|
||||
The device probe found that no device memory had been configured on the
|
||||
DEFEA. Also the DEFEA can be configured with no device memory, this driver
|
||||
requires a mininum of 1K device memory be setup. The ECU (EISA Configuration
|
||||
requires a minimum of 1K device memory be setup. The ECU (EISA Configuration
|
||||
Utility) will need to be run to change the settings.
|
||||
.El
|
||||
.Sh CAVEATS
|
||||
|
||||
@ -101,7 +101,7 @@ the line
|
||||
.Dq Li hint.fxp.0.prefer_iomap="0" .
|
||||
.It "fxp%d: Microcode loaded, int_delay: %d usec bundle_max: %d"
|
||||
The chip has successfully downloaded the microcode, and changed the
|
||||
parametrized values to the given settings.
|
||||
parameterized values to the given settings.
|
||||
.El
|
||||
.Sh SEE ALSO
|
||||
.Xr arp 4 ,
|
||||
|
||||
@ -50,9 +50,9 @@ GMII transceivers, which means it can be used with either copper or
|
||||
Both boards support VLAN tagging/insertion and the 82543 additionally
|
||||
supports TCP/IP checksum offload.
|
||||
.Pp
|
||||
The 82543-T cards use the Marvell 10/100/1000 copper gigabit tranceiver
|
||||
The 82543-T cards use the Marvell 10/100/1000 copper gigabit transceiver
|
||||
chip, which supports autonegotiation of 10, 100 and 1000mbps modes in
|
||||
full or half duplex, however half duplex 1000mbps is not suppoorted.
|
||||
full or half duplex, however half duplex 1000mbps is not supported.
|
||||
.Pp
|
||||
The driver also supports jumbo frames, which can be configured
|
||||
via the interface MTU setting.
|
||||
|
||||
@ -62,7 +62,7 @@ Not all drivers implement all system calls, for example, calling
|
||||
.Xr mmap 2
|
||||
on terminal devices is likely to be not useful at all.
|
||||
.Ss Accessing Devices
|
||||
Most of the devices in a unix-like operating system are accessed
|
||||
Most of the devices in a Unix-like operating system are accessed
|
||||
through so-called
|
||||
.Em device nodes ,
|
||||
sometimes also called
|
||||
|
||||
@ -493,7 +493,7 @@ the kernel will get the value in the following preference:
|
||||
(2) options specified by a sticky option of the advanced API,
|
||||
(3) options specified by using the basic API, and lastly
|
||||
(4) options specified by a socket address.
|
||||
Note that the conflict resolution is undefined in the API specifcation
|
||||
Note that the conflict resolution is undefined in the API specification
|
||||
and implementation dependent.
|
||||
.\"
|
||||
.Ss "Raw IPv6 Sockets"
|
||||
@ -592,7 +592,7 @@ since this checksum is mandatory.
|
||||
For other raw IPv6 sockets (that is, for raw IPv6 sockets created
|
||||
with a third argument other than IPPROTO_ICMPV6), the application
|
||||
must set the new IPV6_CHECKSUM socket option to have the kernel (1)
|
||||
compute and store a psuedo header checksum for output,
|
||||
compute and store a pseudo header checksum for output,
|
||||
and (2) verify the received
|
||||
pseudo header checksum on input,
|
||||
discarding the packet if the checksum is in error.
|
||||
|
||||
@ -174,7 +174,7 @@ very gracefully.
|
||||
Target mode support isn't completely debugged yet.
|
||||
It works reasonably
|
||||
well for Fibre Channel, somewhat well for Qlogic 1040 cards, but
|
||||
doesn't yet work for the other cards (due to last minute unnanounced
|
||||
doesn't yet work for the other cards (due to last minute unannounced
|
||||
changes in firmware interfaces).
|
||||
.Pp
|
||||
Sometimes, when booting, the driver gets stuck waiting for the
|
||||
|
||||
@ -113,7 +113,7 @@ The region's base address cannot be changed.
|
||||
.It MDF_FIXLEN
|
||||
The region's length cannot be changed.
|
||||
.It MDF_FIRMWARE
|
||||
The region is believed to have been established by the system firmare.
|
||||
The region is believed to have been established by the system firmware.
|
||||
.It MDF_ACTIVE
|
||||
The region is currently active.
|
||||
.It MDF_BOGUS
|
||||
@ -169,7 +169,7 @@ An attempt to create a new range failed due to a shortage of hardware
|
||||
resources (eg. descriptor slots).
|
||||
.It Bq Er ENOENT
|
||||
An attempt to remove a range failed because no range matches the descriptor
|
||||
base/length supplued.
|
||||
base/length supplied.
|
||||
.It Bq Er EPERM
|
||||
An attempt to remove a range failed because the range is permanently
|
||||
enabled.
|
||||
|
||||
@ -92,7 +92,7 @@ Configuration data on the drive at channel:target does not match the
|
||||
rest of the array.
|
||||
.It mlx%d: system drive installation aborted
|
||||
.Pp
|
||||
Errors occured preventing one or more system drives from being configured.
|
||||
Errors occurred preventing one or more system drives from being configured.
|
||||
.It mlx%d: new controller configuration found
|
||||
.Pp
|
||||
The controller has detected a configuration on disk which supersedes the
|
||||
|
||||
@ -210,7 +210,7 @@ struct scsi_tape_errors {
|
||||
struct {
|
||||
u_int32_t retries; /* total # retries performed */
|
||||
u_int32_t corrected; /* total # corrections performed */
|
||||
u_int32_t processed; /* total # corrections succssful */
|
||||
u_int32_t processed; /* total # corrections successful */
|
||||
u_int32_t failures; /* total # corrections/retries failed */
|
||||
u_int64_t nbytes; /* total # bytes processed */
|
||||
} wterr, rderr;
|
||||
|
||||
@ -243,14 +243,14 @@ implements a
|
||||
semantic so that when there is a writer in the node, all other requests
|
||||
are queued, and while there are readers, a writer, and any following
|
||||
packets are queued. In the case where there is no reason to queue the
|
||||
data, the input method is called directly, as mentionned above.
|
||||
data, the input method is called directly, as mentioned above.
|
||||
.Pp
|
||||
A node may declare that all requests should be considered as writers,
|
||||
or that requests coming in over a particular hook should be considered to
|
||||
be a writer, or even that packets leaving or entering across a particular
|
||||
hook should always be queued, rather than delivered directly (often useful
|
||||
for interrupt routines who want to get back to the hardware quickly).
|
||||
By default, all controll message packets are considered to be writers
|
||||
By default, all control message packets are considered to be writers
|
||||
unless specifically declared to be a reader in their definition. (see
|
||||
NGM_READONLY in ng_message.h)
|
||||
.Pp
|
||||
@ -365,10 +365,10 @@ Two other methods are also supported by all nodes:
|
||||
.Bl -tag -width xxx
|
||||
.It Receive data message
|
||||
A
|
||||
.Em Netgraph queueable reqest item ,
|
||||
usually refered to as an
|
||||
.Em Netgraph queueable request item ,
|
||||
usually referred to as an
|
||||
.Em item ,
|
||||
is recieved by the function.
|
||||
is received by the function.
|
||||
The item contains a pointer to an mbuf and metadata about the packet.
|
||||
.Pp
|
||||
The node is notified on which hook the item arrived,
|
||||
@ -382,9 +382,9 @@ Similarly the
|
||||
must be freed if it is not to be passed on to another node, by using the
|
||||
.Fn NG_FREE_ITEM
|
||||
macro. If the item still holds references to mbufs or metadata at the time of
|
||||
freeing then they will also be appropriatly freed.
|
||||
freeing then they will also be appropriately freed.
|
||||
Therefore, if there is any chance that the mbuf or metadata will be
|
||||
changed or freed separatly from the item, it is very important
|
||||
changed or freed separately from the item, it is very important
|
||||
that these fields be retrieved using the
|
||||
.Fn NGI_GET_M
|
||||
and
|
||||
@ -450,7 +450,7 @@ other than it will receive all (and only) packets from that hook.
|
||||
This method is called when a control message is addressed to the node.
|
||||
As with the received data, an
|
||||
.Em item
|
||||
is reveived, with a pointer to the control message.
|
||||
is received, with a pointer to the control message.
|
||||
The message can be examined using the
|
||||
.Fn NGI_MSG
|
||||
macro, or completely extracted from the item using the
|
||||
@ -459,7 +459,7 @@ which also removes the reference within the item.
|
||||
If the Item still holds a reference to the message when it is freed
|
||||
(using the
|
||||
.Fn NG_FREE_ITEM
|
||||
macro), then the message will also be freed appropriatly. If the
|
||||
macro), then the message will also be freed appropriately. If the
|
||||
reference has been removed the node must free the message itself using the
|
||||
.Fn NG_FREE_MSG
|
||||
macro.
|
||||
@ -579,7 +579,7 @@ In each of these cases, where a relative addressing mode is
|
||||
used, the recipient is notified of the hook on which the
|
||||
message arrived, as well as
|
||||
the originating node.
|
||||
This allows the option of hop-by-hop distibution of messages and
|
||||
This allows the option of hop-by-hop distribution of messages and
|
||||
state information.
|
||||
Data messages are
|
||||
.Em only
|
||||
@ -623,7 +623,7 @@ over an ISDN line:
|
||||
.Sh Netgraph Structures
|
||||
Structures are defined in
|
||||
.Pa sys/netgraph/netgraph.h
|
||||
(for kernel sructures only of interest to nodes)
|
||||
(for kernel structures only of interest to nodes)
|
||||
and
|
||||
.Pa sys/netgraph/ng_message.h
|
||||
(for message definitions also of interest to user programs).
|
||||
@ -767,7 +767,7 @@ The
|
||||
and
|
||||
.Fn NG_HOOK_SET_RCVMSG hook fn
|
||||
macros can be used to set over-ride methods that will be used in preference
|
||||
to the generic receive data and reveive message functions. To unset these
|
||||
to the generic receive data and receive message functions. To unset these
|
||||
use the macros to set them to NULL. They will only be used for data and
|
||||
messages received on the hook on which they are set.
|
||||
.El
|
||||
@ -897,7 +897,7 @@ field contains a NUL-terminated
|
||||
string version of the message arguments.
|
||||
.El
|
||||
.Pp
|
||||
In general, the arguments field of a control messgage can be any
|
||||
In general, the arguments field of a control message can be any
|
||||
arbitrary C data type. Netgraph includes parsing routines to support
|
||||
some pre-defined datatypes in
|
||||
.Tn ASCII
|
||||
@ -1220,13 +1220,13 @@ vpns using the
|
||||
.Em PPTP
|
||||
node.
|
||||
.It PPPOE
|
||||
A server and client side implememtation of PPPoE. Used in conjunction with
|
||||
A server and client side implementation of PPPoE. Used in conjunction with
|
||||
either
|
||||
.Xr ppp 8
|
||||
or the
|
||||
.Em mpd port .
|
||||
.It BRIDGE
|
||||
This node, togther with the ethernet nodes allows a very flexible
|
||||
This node, together with the ethernet nodes allows a very flexible
|
||||
bridging system to be implemented.
|
||||
.It KSOCKET
|
||||
This intriguing node looks like a socket to the system but diverts
|
||||
@ -1270,7 +1270,7 @@ are freed by the recipient. As in the case above, the addresses
|
||||
associated with the message are freed by whatever allocated them so the
|
||||
recipient should copy them if it wants to keep that information.
|
||||
.It 4
|
||||
Both control mesages and data are delivered and queued with
|
||||
Both control messages and data are delivered and queued with
|
||||
a netgraph
|
||||
.Em item .
|
||||
The item must be freed using
|
||||
|
||||
@ -96,7 +96,7 @@ socket address parameter should be supplied as an argument.
|
||||
.It Dv NGM_KSOCKET_LISTEN
|
||||
This functions exactly like the
|
||||
.Xr listen 2
|
||||
system call. The backlog paramter (a single 32 bit
|
||||
system call. The backlog parameter (a single 32 bit
|
||||
.Dv int )
|
||||
should be supplied as an argument.
|
||||
.It Dv NGM_KSOCKET_CONNECT
|
||||
|
||||
@ -105,7 +105,7 @@ The
|
||||
field enables traffic flow through the node.
|
||||
The
|
||||
.Va enableDelayedAck
|
||||
field enables delayed acknowledgement (maximum 250 miliseconds), which
|
||||
field enables delayed acknowledgement (maximum 250 milliseconds), which
|
||||
is a useful optimization and should generally be turned on.
|
||||
.Va enableAlwaysAck
|
||||
field enables sending acknowledgements with every data packet, which
|
||||
|
||||
@ -79,7 +79,7 @@ The
|
||||
.Nm
|
||||
node type was implemented in
|
||||
.Fx 3.5
|
||||
but incorprated into
|
||||
but incorporated into
|
||||
.Fx
|
||||
in
|
||||
.Fx 5.0 .
|
||||
|
||||
@ -77,7 +77,7 @@ The DP83820 supports TCP/IP checksum offload and
|
||||
VLAN tagging/insertion as well as a 2048-bit multicast hash filter
|
||||
and up to 4 pattern match buffers.
|
||||
.Pp
|
||||
Most cards also use the DP83861 10/100/1000 copper gigabit tranceiver
|
||||
Most cards also use the DP83861 10/100/1000 copper gigabit transceiver
|
||||
chip, which supports autonegotiation of 10, 100 and 1000mbps modes in
|
||||
full or half duplex.
|
||||
.Pp
|
||||
|
||||
@ -113,7 +113,7 @@ the network connection (e.g. a cable fault).
|
||||
The driver failed to allocate an mbuf for the receiver ring.
|
||||
.It "pcn%d: no memory for tx list"
|
||||
The driver failed to allocate an mbuf for the transmitter ring when
|
||||
allocating a pad buffer or collapsing an mbuf chain into a clusisr.
|
||||
allocating a pad buffer or collapsing an mbuf chain into a cluster.
|
||||
.It "pcn%d: chip is in D3 power state -- setting to D0"
|
||||
This message applies only to adapters which support power
|
||||
management.
|
||||
|
||||
@ -532,7 +532,7 @@ struct screeninfo {
|
||||
/* on write, if -1, no change */
|
||||
int vga_family; /* if adaptor_type = VGA, this reflects*/
|
||||
/* the chipset family after a read */
|
||||
/* nothing happenes on write ... */
|
||||
/* nothing happens on write ... */
|
||||
int vga_type; /* if adaptor_type = VGA, this reflects*/
|
||||
/* the chipset after a read */
|
||||
/* nothing happenes on write ... */
|
||||
|
||||
@ -770,7 +770,7 @@ In contrast, some pad products, e.g. some verions of ALPS GlidePoint
|
||||
and Interlink VersaPad, treat the tapping action
|
||||
as fourth button events.
|
||||
.Pp
|
||||
It is reported that Interlink VersaPad rquires both
|
||||
It is reported that Interlink VersaPad requires both
|
||||
.Em HOOKRESUME
|
||||
and
|
||||
.Em INITAFTERSUSPEND
|
||||
|
||||
@ -63,7 +63,7 @@ SK-9844 SK-NET GE-SX dual port, multimode fiber adapter
|
||||
The SysKonnect adapters consist of two main components: the XaQti Corp.
|
||||
XMAC II gigabit MAC and the SysKonnect GEnesis controller ASIC.
|
||||
The
|
||||
XMAC provides the gigabit MAC and PHY suspport while the GEnesis
|
||||
XMAC provides the gigabit MAC and PHY support while the GEnesis
|
||||
provides an interface to the PCI bus, DMA support, packet buffering
|
||||
and arbitration.
|
||||
The GEnesis can control up to two XMACs simultaneously,
|
||||
@ -78,7 +78,7 @@ The
|
||||
driver configures dual port SysKonnect adapters such that each XMAC
|
||||
is treated as a separate logical network interface.
|
||||
Both ports can
|
||||
operate indepenently of each other and can be connected to separate
|
||||
operate independently of each other and can be connected to separate
|
||||
networks.
|
||||
The SysKonnect driver software currently only uses the
|
||||
second port on dual port adapters for failover purposes: if the link
|
||||
|
||||
@ -45,7 +45,7 @@ in a read buffer.
|
||||
Special values defined are:
|
||||
.Bl -tag -width SNP_TTYCLOSE
|
||||
.It Dv SNP_OFLOW
|
||||
device overflow occured, device detached.
|
||||
device overflow occurred, device detached.
|
||||
.It Dv SNP_TTYCLOSE
|
||||
tty not attached.
|
||||
.It Dv SNP_DETACH
|
||||
|
||||
@ -41,7 +41,7 @@ Protocol (LCP) of the
|
||||
.Em point to point protocol (PPP)
|
||||
as described in RFC 1661. Note that this layer does not provide
|
||||
network interfaces of its own, it is rather intended to be layered on
|
||||
top of drivers providing a synchronuous point-to-point connection that
|
||||
top of drivers providing a synchronous point-to-point connection that
|
||||
wish to run a PPP stack over it. The corresponding network interfaces
|
||||
have to be provided by these hardware drivers.
|
||||
.Pp
|
||||
|
||||
@ -122,7 +122,7 @@ interface filters out the following packets.
|
||||
Note that the checks are no way complete:
|
||||
.Bl -bullet
|
||||
.It
|
||||
Packets with IPv4 unspecified addrss as outer IPv4 source/destination
|
||||
Packets with IPv4 unspecified address as outer IPv4 source/destination
|
||||
.Pq Li 0.0.0.0/8
|
||||
.It
|
||||
Packets with loopback address as outer IPv4 source/destination
|
||||
@ -144,7 +144,7 @@ Ingress filter can be turned off by
|
||||
.Dv IFF_LINK2
|
||||
bit.
|
||||
.It
|
||||
The same set of rules are appplied against the IPv4 address embedded into
|
||||
The same set of rules are applied against the IPv4 address embedded into
|
||||
inner IPv6 address, if the IPv6 address matches 6to4 prefix.
|
||||
.El
|
||||
.Pp
|
||||
|
||||
@ -275,7 +275,7 @@ By default, its value is
|
||||
This options instructs the driver to convert leading spaces into tabs
|
||||
when copying data into cut buffer.
|
||||
This might be useful to preserve
|
||||
identation when copying tab-idented text.
|
||||
indentation when copying tab-indented text.
|
||||
.It Dv SC_DISABLE_DDBKEY
|
||||
This option disables the ``debug'' key (by default, it is
|
||||
.Dv Alt-Esc ,
|
||||
|
||||
@ -225,7 +225,7 @@ The number of packets allowed to be in-flight during the
|
||||
.Tn TCP
|
||||
slow-start phase to local machines in the same subnet.
|
||||
.It tcp.msl
|
||||
The Maximum Segment Lifetime, in millseconds, for a packet.
|
||||
The Maximum Segment Lifetime, in milliseconds, for a packet.
|
||||
.It tcp.keepinit
|
||||
Timeout, in milliseconds, for new, non-established TCP connections.
|
||||
.It tcp.keepidle
|
||||
|
||||
@ -1005,7 +1005,7 @@ on output) */
|
||||
.It Dv ONOCR
|
||||
/* do not transmit CRs on column 0 */
|
||||
.It Dv ONLRET
|
||||
/* on the termianl NL performs the CR function */
|
||||
/* on the terminal NL performs the CR function */
|
||||
.El
|
||||
.Pp
|
||||
If
|
||||
|
||||
@ -75,7 +75,7 @@ driver supports the following media types:
|
||||
Enable autoselection of the media type and options.
|
||||
Note that this
|
||||
option is only available on those PHYs that support autonegotiation.
|
||||
Also, the PHY will not advertise those modes that have been explcitly
|
||||
Also, the PHY will not advertise those modes that have been explicitly
|
||||
disabled using the following media options.
|
||||
.It 10baseT/UTP
|
||||
Set 10Mbps operation
|
||||
|
||||
@ -138,7 +138,7 @@ driver can attach.
|
||||
.Sh USB CONTROLLER INTERFACE
|
||||
Use the following to get access to the
|
||||
.Tn USB
|
||||
specific structurs and defines.
|
||||
specific structures and defines.
|
||||
.Bd -literal
|
||||
#include <sys/dev/usb.h>
|
||||
.Ed
|
||||
|
||||
@ -324,7 +324,7 @@ assigns default names to plexes and subdisks, although they may be overridden.
|
||||
We do not recommend overriding the default names. Experience with the
|
||||
.if t Veritas\(tm
|
||||
.if n Veritas(tm)
|
||||
volume manager, which allows arbitary naming of objects, has shown that this
|
||||
volume manager, which allows arbitrary naming of objects, has shown that this
|
||||
flexibility does not bring a significant advantage, and it can cause confusion.
|
||||
.sp
|
||||
Names may contain any non-blank character, but it is recommended to restrict
|
||||
@ -685,7 +685,7 @@ down and up again. No updates were lost, but it is possible that the subdisk
|
||||
has been damaged. We won't read from this subdisk if we have a choice. If this
|
||||
is the only subdisk which covers this address space in the plex, we set its
|
||||
state to up under these circumstances, so this status implies that there is
|
||||
another subdisk to fulfil the request.
|
||||
another subdisk to fulfill the request.
|
||||
.It Li up
|
||||
A subdisk entry which has been created completely. All fields are correct, the
|
||||
disk has been updated, and the data is valid.
|
||||
|
||||
@ -47,7 +47,7 @@ The driver has been extended to the ZIP+ drive which is based on the
|
||||
Iomega Matchmaker Parallel to SCSI interface.
|
||||
.Sh USAGE
|
||||
The driver should let you use a printer connected to the drive while
|
||||
transfering data.
|
||||
transferring data.
|
||||
.Pp
|
||||
DOS and
|
||||
.Fx
|
||||
@ -83,7 +83,7 @@ bootflags to force other modes.
|
||||
.Xr scsi 4
|
||||
.Sh BUGS
|
||||
During boot, the driver firstly try to detect a classic ZIP, then a ZIP+.
|
||||
The ZIP+ detection is intrusive and may send errorneous charaters to your
|
||||
The ZIP+ detection is intrusive and may send erroneous characters to your
|
||||
printer if the drive is not connected to your parallel port.
|
||||
.Sh HISTORY
|
||||
The
|
||||
|
||||
@ -176,4 +176,4 @@ supplied buffer address and begin DMAing from the wrong location.
|
||||
This buffer copying impairs transmit performance on slower systems but can't
|
||||
be avoided.
|
||||
On faster machines (e.g. a Pentium II), the performance
|
||||
impact is much less noticable.
|
||||
impact is much less noticeable.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user