| rl.4 (41537) | rl.4 (41569) |
|---|---|
| 1.\" Copyright (c) 1997, 1998 2.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 14 unchanged lines hidden (view full) --- 23.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 24.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 25.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 26.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 27.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 28.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 29.\" THE POSSIBILITY OF SUCH DAMAGE. 30.\" | 1.\" Copyright (c) 1997, 1998 2.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 14 unchanged lines hidden (view full) --- 23.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 24.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 25.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 26.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 27.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 28.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 29.\" THE POSSIBILITY OF SUCH DAMAGE. 30.\" |
| 31.\" $Id: rl.4,v 1.3 1998/11/18 21:05:11 wpaul Exp $ | 31.\" $Id: rl.4,v 1.8 1998/12/07 00:17:23 wpaul Exp $ |
| 32.\" 33.Dd November 4, 1998 34.Dt RL 4 i386 35.Os FreeBSD 36.Sh NAME 37.Nm rl 38.Nd 39RealTek 8129/8139 fast ethernet device driver 40.Sh SYNOPSIS 41.Cd "device rl0" 42.Sh DESCRIPTION 43The 44.Nm 45driver provides support for PCI ethernet adapters and embedded 46controllers based on the RealTek 8129 and 8139 fast ethernet controller 47chips. This includes the Allied Telesyn AT2550, Genius GF100TXR, 48NDC Communications NE100TX-E, OvisLink LEF-8129TX, OvisLink LEF-8139TX, 49Netronix Inc. EA-1210 NetEther 10/100, KTX-9130TX 10/100 Fast Ethernet, | 32.\" 33.Dd November 4, 1998 34.Dt RL 4 i386 35.Os FreeBSD 36.Sh NAME 37.Nm rl 38.Nd 39RealTek 8129/8139 fast ethernet device driver 40.Sh SYNOPSIS 41.Cd "device rl0" 42.Sh DESCRIPTION 43The 44.Nm 45driver provides support for PCI ethernet adapters and embedded 46controllers based on the RealTek 8129 and 8139 fast ethernet controller 47chips. This includes the Allied Telesyn AT2550, Genius GF100TXR, 48NDC Communications NE100TX-E, OvisLink LEF-8129TX, OvisLink LEF-8139TX, 49Netronix Inc. EA-1210 NetEther 10/100, KTX-9130TX 10/100 Fast Ethernet, |
| 50Encore ENL832-TX 10/100 M PCI, Longshine LCS-8038TX-R and various 51other cheap adapters. It also supports the Accton EN1207D which has a | 50Encore ENL832-TX 10/100 M PCI, Longshine LCS-8038TX-R, the 51SMC EtherEZ 1211-TX, and various other cheap adapters. 52It also supports the Accton EN1207D which has a |
| 52chip labeled MPX5030 (or MPX5038) which appears to be a RealTek workalike. 53.Pp 54The RealTek controllers use bus master DMA but do not use a 55descriptor-based data transfer mechanism. The receiver uses a 56single fixed size ring buffer from which packets must be copied 57into mbufs. For transmission, there are only four outbound packet 58address registers which require all outgoing packets to be stored 59as contiguous buffers. Furthermore, outbound packet buffers must --- 57 unchanged lines hidden (view full) --- 117.It "rl%d: couldn't map interrupt" 118A fatal initialization error has occurred. 119.It "rl%d: watchdog timeout" 120The device has stopped responding to the network, or there is a problem with 121the network connection (cable). 122.It "rl%d: no memory for rx list" 123The driver failed to allocate an mbuf for the receiver ring. 124.It "rl%d: no memory for tx list" | 53chip labeled MPX5030 (or MPX5038) which appears to be a RealTek workalike. 54.Pp 55The RealTek controllers use bus master DMA but do not use a 56descriptor-based data transfer mechanism. The receiver uses a 57single fixed size ring buffer from which packets must be copied 58into mbufs. For transmission, there are only four outbound packet 59address registers which require all outgoing packets to be stored 60as contiguous buffers. Furthermore, outbound packet buffers must --- 57 unchanged lines hidden (view full) --- 118.It "rl%d: couldn't map interrupt" 119A fatal initialization error has occurred. 120.It "rl%d: watchdog timeout" 121The device has stopped responding to the network, or there is a problem with 122the network connection (cable). 123.It "rl%d: no memory for rx list" 124The driver failed to allocate an mbuf for the receiver ring. 125.It "rl%d: no memory for tx list" |
| 125The driver failed to allocate an mbuf for the transmitter ring when | 126The driver fauled to allocate an mbuf for the transmitter ring when |
| 126allocating a pad buffer or collapsing an mbuf chain into a cluster. 127.It "rl%d: chip is in D3 power state -- setting to D0" 128This message applies only to adapters which support power 129management. Some operating systems place the controller in low power 130mode when shutting down, and some PCI BIOSes fail to bring the chip 131out of this state before configuring it. The controller loses all of 132its PCI configuration in the D3 state, so if the BIOS does not set 133it back to full power mode in time, it won't be able to configure it --- 58 unchanged lines hidden --- | 127allocating a pad buffer or collapsing an mbuf chain into a cluster. 128.It "rl%d: chip is in D3 power state -- setting to D0" 129This message applies only to adapters which support power 130management. Some operating systems place the controller in low power 131mode when shutting down, and some PCI BIOSes fail to bring the chip 132out of this state before configuring it. The controller loses all of 133its PCI configuration in the D3 state, so if the BIOS does not set 134it back to full power mode in time, it won't be able to configure it --- 58 unchanged lines hidden --- |