diff options
author | sheldonh <sheldonh@FreeBSD.org> | 2000-03-03 14:05:08 +0000 |
---|---|---|
committer | sheldonh <sheldonh@FreeBSD.org> | 2000-03-03 14:05:08 +0000 |
commit | 88dd9b4faa11f5f0aa21cbd43fb72503a67b4229 (patch) | |
tree | 69062af71195d869d2c940c1869ddf1621cbabfb /share/man/man4/wb.4 | |
parent | 1b7dce690e9fb2a298fb1e3bedc8186e71b877a3 (diff) | |
download | FreeBSD-src-88dd9b4faa11f5f0aa21cbd43fb72503a67b4229.zip FreeBSD-src-88dd9b4faa11f5f0aa21cbd43fb72503a67b4229.tar.gz |
Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
Diffstat (limited to 'share/man/man4/wb.4')
-rw-r--r-- | share/man/man4/wb.4 | 48 |
1 files changed, 32 insertions, 16 deletions
diff --git a/share/man/man4/wb.4 b/share/man/man4/wb.4 index 3a20b62..a959124 100644 --- a/share/man/man4/wb.4 +++ b/share/man/man4/wb.4 @@ -45,16 +45,20 @@ The .Nm driver provides support for PCI ethernet adapters and embedded controllers based on the Winbond W89C840F fast ethernet controller -chip. This includes the Trendware TE100-PCIE and various other cheap -boards. The 840F should not be confused with the 940F, which is +chip. +This includes the Trendware TE100-PCIE and various other cheap +boards. +The 840F should not be confused with the 940F, which is an NE2000 clone and only supports 10Mbps speeds. .Pp The Winbond controller uses bus master DMA and is designed to be -a DEC 'tulip' workalike. It differs from the standard DEC design +a DEC 'tulip' workalike. +It differs from the standard DEC design in several ways: the control and status registers are spaced 4 bytes apart instead of 8, and the receive filter is programmed through registers rather than by downloading a special setup frame via -the transmit DMA engine. Using an external PHY, the Winbond chip +the transmit DMA engine. +Using an external PHY, the Winbond chip supports both 10 and 100Mbps speeds in either full or half duplex. .Pp The @@ -63,21 +67,25 @@ driver supports the following media types: .Pp .Bl -tag -width xxxxxxxxxxxxxxxxxxxx .It autoselect -Enable autoselection of the media type and options. This is only +Enable autoselection of the media type and options. +This is only supported if the PHY chip attached to the Winbond controller -supports NWAY autonegotiation. The user can manually override +supports NWAY autonegotiation. +The user can manually override the autoselected mode by adding media options to the .Pa /etc/rc.conf file. .It 10baseT/UTP -Set 10Mbps operation. The +Set 10Mbps operation. +The .Ar mediaopt option can also be used to select either .Ar full-duplex or .Ar half-duplex modes. .It 100baseTX -Set 100Mbps (fast ethernet) operation. The +Set 100Mbps (fast ethernet) operation. +The .Ar mediaopt option can also be used to select either .Ar full-duplex @@ -117,20 +125,25 @@ The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. .It "wb%d: chip is in D3 power state -- setting to D0" This message applies only to adapters which support power -management. Some operating systems place the controller in low power +management. +Some operating systems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip -out of this state before configuring it. The controller loses all of +out of this state before configuring it. +The controller loses all of its PCI configuration in the D3 state, so if the BIOS does not set it back to full power mode in time, it won't be able to configure it -correctly. The driver tries to detect this condition and bring +correctly. +The driver tries to detect this condition and bring the adapter back to the D0 (full power) state, but this may not be -enough to return the driver to a fully operational condition. If +enough to return the driver to a fully operational condition. +If you see this message at boot time and the driver fails to attach the device as a network interface, you will have to perform second warm boot to have the device properly configured. .Pp Note that this condition only occurs when warm booting from another -operating system. If you power down your system prior to booting +operating system. +If you power down your system prior to booting .Fx , the card should be configured correctly. .El @@ -151,11 +164,14 @@ driver was written by .An Bill Paul Aq wpaul@ctr.columbia.edu . .Sh BUGS The Winbond chip seems to behave strangely in some cases when the -link partner switches modes. If for example both sides are set to +link partner switches modes. +If for example both sides are set to 10Mbps half-duplex, and the other end is changed to 100Mbps full-duplex, the Winbond's receiver suddenly starts writing trash -all over the RX descriptors. The +all over the RX descriptors. +The .Nm driver handles this by forcing a reset of both the controller -chip and attached PHY. This is drastic, but it appears to be the +chip and attached PHY. +This is drastic, but it appears to be the only way to recover properly from this condition. |