Man page police.

This commit is contained in:
mpp 1997-01-25 20:42:09 +00:00
parent 06c77ecb65
commit 326ab14b20
9 changed files with 16 additions and 43 deletions

View File

@ -43,11 +43,10 @@ Equipment DC21x4x based self-contained Ethernet chips.
It supports the DEC PCI DE435 card, DEC EISA DE425, DEC DE450, SMC 9332,
ZNYX ZX314, and others based on the 21040 and 21041 Ethernet controllers or
the 21140[A] Fast 100Base-T Ethernet controller.
.Pp
.Sh DIAGNOSTICS
.Bl -diag
.It "de%d: waking device from sleep/snooze mode"
The 21041 and 21140A chips support suppending the operation of the card.
The 21041 and 21140A chips support suspending the operation of the card.
.It "de%d: error: desired IRQ of %d does not match device's actual IRQ of %d"
The device probe detected that the board is configured for a different
interrupt than the one specified in the kernel configuration file.
@ -59,14 +58,11 @@ devices allowed in a single machine.
.It "de%d: not configured; 21140 pass 1.1 required (%d.%d found)"
Certain revisions of the chipset are not supported by this driver.
.El
.Pp
.Sh CAVEATS
Since the 21040 is available on both EISA and PCI boards, one must be careful
in how defines the 21040 in the kernel config file.
.Pp
.Sh BUGS
Currently the driver does not support multicast.
.Pp
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,

View File

@ -31,7 +31,7 @@
.Sh NAME
.Nm fxp
.Nd
Intel EtherExpress Pro/100B ethernet device driver
Intel EtherExpress Pro/100B Ethernet device driver
.Sh SYNOPSIS
.Cd "device fxp0"
.Sh DESCRIPTION
@ -39,8 +39,6 @@ The
.Nm
driver provides support for the EtherExpress Pro/100B PCI Fast Ethernet
adapter based on the Intel i82557 Ethernet chip.
.Pp
.Pp
.Sh DIAGNOSTICS
.Bl -diag
.It "fxp%d: couldn't map memory"
@ -53,7 +51,6 @@ There are not enough mbuf's available for allocation.
The device has stopped responding to the network, or there is a problem with
the network connection (cable).
.El
.Pp
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,

View File

@ -43,11 +43,10 @@ Equipment DC21x4x based self-contained Ethernet chips.
It supports the DEC PCI DE435 card, DEC EISA DE425, DEC DE450, SMC 9332,
ZNYX ZX314, and others based on the 21040 and 21041 Ethernet controllers or
the 21140[A] Fast 100Base-T Ethernet controller.
.Pp
.Sh DIAGNOSTICS
.Bl -diag
.It "de%d: waking device from sleep/snooze mode"
The 21041 and 21140A chips support suppending the operation of the card.
The 21041 and 21140A chips support suspending the operation of the card.
.It "de%d: error: desired IRQ of %d does not match device's actual IRQ of %d"
The device probe detected that the board is configured for a different
interrupt than the one specified in the kernel configuration file.
@ -59,14 +58,11 @@ devices allowed in a single machine.
.It "de%d: not configured; 21140 pass 1.1 required (%d.%d found)"
Certain revisions of the chipset are not supported by this driver.
.El
.Pp
.Sh CAVEATS
Since the 21040 is available on both EISA and PCI boards, one must be careful
in how defines the 21040 in the kernel config file.
.Pp
.Sh BUGS
Currently the driver does not support multicast.
.Pp
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,

View File

@ -31,7 +31,7 @@
.Sh NAME
.Nm fxp
.Nd
Intel EtherExpress Pro/100B ethernet device driver
Intel EtherExpress Pro/100B Ethernet device driver
.Sh SYNOPSIS
.Cd "device fxp0"
.Sh DESCRIPTION
@ -39,8 +39,6 @@ The
.Nm
driver provides support for the EtherExpress Pro/100B PCI Fast Ethernet
adapter based on the Intel i82557 Ethernet chip.
.Pp
.Pp
.Sh DIAGNOSTICS
.Bl -diag
.It "fxp%d: couldn't map memory"
@ -53,7 +51,6 @@ There are not enough mbuf's available for allocation.
The device has stopped responding to the network, or there is a problem with
the network connection (cable).
.El
.Pp
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,

View File

@ -31,7 +31,7 @@
.Sh NAME
.Nm ix
.Nd
EtherExpress ethernet device driver
Intel EtherExpress Ethernet device driver
.Sh SYNOPSIS
.Cd "device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr"
.Sh DESCRIPTION
@ -42,7 +42,6 @@ card based on the Intel i82586 chip.
.Pp
If the IRQ is autodetected if the kernel configuration file has "irq?" or
doesn't specify an IRQ at all.
.Pp
.Sh DIAGNOSTICS
.Bl -diag
.It "ix%d: WARNING: board is configured for IRQ %d, using %d"
@ -52,26 +51,23 @@ be used in this case.
.It "ix%d: invalid irq (%d)"
An invalid IRQ was specified. This is a fatal error.
.It "ix%d: ixstart: Packet length=%d > MTU=%d"
The length of the Ethernet packet read was larger than the maxium transfer
The length of the Ethernet packet read was larger than the maximum transfer
unit allowed. This message suggests an error in the driver. It probably
should be concidered fatal and the driver shut down. Currently this does
should be considered fatal and the driver shut down. Currently this does
not happen though.
.It "ix%d: device timeout"
The device has stopped responding to the network, or there is a problem with
the network connection (cable). Make sure the network connection in use
is the same one the probe read from the EEPROM.
.El
.Pp
.Sh CAVEATS
The driver will use the IRQ specified in the kernel configuration file
if it does not match the board setting.
The type of network connector used (AUI, BNC, TPE) is probed from the EEPROM.
If this does not match the interface actually in use, timeout errors will
occur.
.Pp
.Sh BUGS
Currently the driver does not support multicast.
.Pp
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,

View File

@ -31,7 +31,7 @@
.Sh NAME
.Nm le
.Nd
ethernet device driver
DEC EtherWORKS II/III Ethernet device driver
.Sh SYNOPSIS
.Cd "device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr"
.Sh DESCRIPTION
@ -63,7 +63,7 @@ should be built.
The
.Nm
driver depends on the information in the EEPROM being correct.
If this error occurs, please recofigure the card.
If this error occurs, please reconfigure the card.
.It "le%d: fatal RXD error, attempting recovery"
.It "le%d: recovery failed -- board disabled"
A receive error occurred. The driver will attempt to recover from this

View File

@ -31,7 +31,7 @@
.Sh NAME
.Nm lnc
.Nd
ethernet device driver
AMD Lance/PCnet Ethernet device driver
.Sh SYNOPSIS
.Cd "device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr"
.Sh DESCRIPTION
@ -42,19 +42,17 @@ including the Am7990 and Am79C960.
The Ethernet cards supported by the
.Nm
interface are:
.Pp
.Bl -tag -width -offset ident -compat
.It Novell NE2100
.It Novell NE32-VL
.It Isolan BICC
.It Digital DEPCA
.El
.Pp
.Sh DIAGNOSTICS
.Bl -diag
.It "lnc%d: Framming error"
A framming error occured. This means a CRC error also occurred.
This caused the driver to drop the packet that contained the framming error.
.It "lnc%d: Framing error"
A framing error occurred. This means a CRC error also occurred.
This caused the driver to drop the packet that contained the framing error.
.It "lnc%d: Receive CRC error
The received Ethernet frame failed the CRC checksum.
This caused the driver to drop the packet that failed the checksum.
@ -96,11 +94,9 @@ is the same one the card is configured for.
.It "lnc%d: Transmit buffer error -- Resetting"
.It "lnc%d: Transmit underflow error -- Resetting"
.El
.Pp
.Sh BUGS
This driver has the potential of being the most verbose of any of the
Ethernet device drivers.
.Pp
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,

View File

@ -31,7 +31,7 @@
.Sh NAME
.Nm ze
.Nd
PCMCIA Ethernet device driver
IBM/National Semiconductor PCMCIA Ethernet device driver
.Sh SYNOPSIS
.Cd "device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr"
.Sh DESCRIPTION
@ -45,7 +45,6 @@ The
.Nm
driver is based on the device driver for National Semiconductor DS8390
Ethernet adapter.
.Pp
.Sh DIAGNOSTICS
.Bl -diag
.It "ze%d: device timeout, isr=%02x, imr=%02x, imask=%04x"
@ -55,17 +54,14 @@ the network connection (cable).
This error is sometimes seen on early revisions of the Ethernet driver chip
under high load -- the byte order of the length gets switched.
.El
.Pp
.Sh CAVEATS
This driver is only known to work with IBM Credit Card Adapter for Ethernet,
but could probably work with other PCMCIA cards also, if it were modified
to get the locations of the PCMCIA configuration option register (COR)
by parsing the configuration tuples, rather than by hard-coding in
the value expected by IBM's card.
.Pp
.Sh BUGS
Currently the driver does not support multicast.
.Pp
.Sh SEE ALSO
.Xr arp 4 ,
.Xr netintro 4 ,
@ -73,8 +69,7 @@ Currently the driver does not support multicast.
.Sh HISTORY
The
.Nm
device driver first appeared in
.Fx 1.1.5 .
device driver first appeared in FreeBSD 1.1.5.
.Sh AUTHORS
The
.Nm

View File

@ -31,7 +31,7 @@
.Sh NAME
.Nm zp
.Nd
PCMCIA Ethernet device driver
3Com PCMCIA Etherlink III Ethernet device driver
.Sh SYNOPSIS
.Cd "device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr"
.Sh DESCRIPTION