1 .\" Copyright (c) 1997, 1998
2 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by Bill Paul.
15 .\" 4. Neither the name of the author nor the names of any co-contributors
16 .\" may be used to endorse or promote products derived from this software
17 .\" without specific prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
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.
39 Lite-On 82c168/82c169 PNIC fast ethernet device driver
45 driver provides support for PCI ethernet adapters and embedded
46 controllers based on the Lite-On 82c168 and 82c169 fast ethernet
47 controller chips. This includes the LinkSys LNE100TX, the
48 Bay Networks Netgear FA310TX revision D1, the Matrox Networks
49 FastNIC 10/100, the Kingston KNE110TX (EtherRx VP),
50 and various other commodity fast ethernet cards.
52 The Lite-On chips use bus master DMA and are designed to be
53 DEC 'tulip' workalikes. Many vendors that formerly based their
54 designs around the DEC 21x4x devices are now using the PNIC
55 instead. The chips support both an internal transceiver
56 and external transceivers via an MII bus. The Lite-On parts are
57 advertised as being register compatible with the DEC 21x4x
58 controllers, however there are some differences in the way the
59 EEPROM and MII access is done. The PNIC controllers support both
60 10 and 100Mbps speeds in either full or half duplex.
64 driver supports the following media types:
66 .Bl -tag -width xxxxxxxxxxxxxxxxxxxx
68 Enable autoselection of the media type and options.
69 The user can manually override
70 the autoselected mode by adding media options to the
74 Set 10Mbps operation. The
76 option can also be used to select either
79 .Ar half-duplex modes.
81 Set 100Mbps (fast ethernet) operation. The
83 option can also be used to select either
92 driver supports the following media options:
94 .Bl -tag -width xxxxxxxxxxxxxxxxxxxx
96 Force full duplex operation
98 Force half duplex operation.
101 Note that the 100baseTX media type is only available if supported
103 For more information on configuring this device, see
107 .It "pn%d: couldn't map memory"
108 A fatal initialization error has occurred.
109 .It "pn%d: couldn't map interrupt"
110 A fatal initialization error has occurred.
111 .It "pn%d: watchdog timeout"
112 The device has stopped responding to the network, or there is a problem with
113 the network connection (cable).
114 .It "pn%d: no memory for rx list"
115 The driver failed to allocate an mbuf for the receiver ring.
116 .It "pn%d: no memory for tx list"
117 The driver failed to allocate an mbuf for the transmitter ring when
118 allocating a pad buffer or collapsing an mbuf chain into a cluster.
119 .It "pn%d: chip is in D3 power state -- setting to D0"
120 This message applies only to adapters which support power
121 management. Some operating systems place the controller in low power
122 mode when shutting down, and some PCI BIOSes fail to bring the chip
123 out of this state before configuring it. The controller loses all of
124 its PCI configuration in the D3 state, so if the BIOS does not set
125 it back to full power mode in time, it won't be able to configure it
126 correctly. The driver tries to detect this condition and bring
127 the adapter back to the D0 (full power) state, but this may not be
128 enough to return the driver to a fully operational condition. If
129 you see this message at boot time and the driver fails to attach
130 the device as a network interface, you will have to perform second
131 warm boot to have the device properly configured.
133 Note that this condition only occurs when warm booting from another
134 operating system. If you power down your system prior to booting
136 the card should be configured correctly.
145 device driver first appeared in
150 driver was written by
151 .An Bill Paul Aq wpaul@ctr.columbia.edu .
153 The internal NWAY support on the 82c168 chip is horribly broken, which
154 means that autoselection will not work, except maybe for half-duplex
155 10Mbps links. In order to use other modes (e.g. 100Mbps) it will be
159 to set the interface manually. Autoselection for 82c169 boards using
160 MII transceivers should work correctly.