1.\" Copyright (c) Berkeley Software Design, Inc.
2.\" Copyright (c) 1997, 1998, 1999, 2000
3.\" Bill Paul <wpaul@osd.bsdi.com>. All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\" notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\" notice, this list of conditions and the following disclaimer in the
12.\" documentation and/or other materials provided with the distribution.
13.\" 3. All advertising materials mentioning features or use of this software
14.\" must display the following acknowledgement:
15.\" This product includes software developed by Bill Paul.
16.\" 4. Neither the name of the author nor the names of any co-contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
24.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
25.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
26.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
27.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
28.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
29.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
30.\" THE POSSIBILITY OF SUCH DAMAGE.
31.\"
32.\" $FreeBSD: head/share/man/man4/pcn.4 137881 2004-11-19 03:47:01Z obrien $
33.\"
34.Dd September 13, 2004
35.Dt PCN 4
36.Os
37.Sh NAME
38.Nm pcn
39.Nd "AMD PCnet/PCI Fast Ethernet device driver"
40.Sh SYNOPSIS
41.Cd "device miibus"
42.Cd "device pcn"
43.Sh DESCRIPTION
44The
45.Nm
46driver provides support for PCI Ethernet adapters and embedded
47controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III,
48PCnet/PRO and PCnet/Home Ethernet controller chips.
49Supported NIC's include the Allied Telesyn AT-2700 familly.
50.Pp
51The PCnet/PCI chips include a 100Mbps Ethernet MAC and support
52both a serial and MII-compliant transceiver interface.
53They use a bus master DMA and a scatter/gather descriptor scheme.
54The AMD chips provide a mechanism for zero-copy receive,
55providing good performance in server environments.
56Receive address filtering is provided using a single perfect filter entry
57for the station address and a 64-bit multicast hash table.
58.Pp
59The
60.Nm
61driver supports the following media types:
62.Pp
63.Bl -tag -width 10baseTXUTP
64.It autoselect
65Enable autoselection of the media type and options.
66The user can manually override
67the autoselected mode by adding media options to
68.Xr rc.conf 5 .
69.It 10baseT/UTP
70Set 10Mbps operation.
71The
72.Xr ifconfig 8
73.Cm mediaopt
74option can also be used to select either
75.Sq full-duplex
76or
77.Sq half-duplex
78modes.
79.It 100baseTX
80Set 100Mbps (Fast Ethernet) operation.
81The
82.Xr ifconfig 8
83.Cm mediaopt
84option can also be used to select either
85.Sq full-duplex
86or
87.Sq half-duplex
88modes.
89.El
90.Pp
91The
92.Nm
93driver supports the following media options:
94.Pp
95.Bl -tag -width full-duplex
96.It full-duplex
97Force full duplex operation
98.It half-duplex
99Force half duplex operation.
100.El
101.Pp
102For more information on configuring this device, see
103.Xr ifconfig 8 .
104.Sh HARDWARE
105The
106.Nm
107driver supports adapters and embedded controllers based on the AMD PCnet/FAST,
108PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:
109.Pp
110.Bl -bullet -compact
111.It
112AMD Am53C974/Am79C970/Am79C974 PCnet-PCI
113.It
114AMD Am79C970A PCnet-PCI II
115.It
116AMD Am79C971 PCnet-FAST
117.It
118AMD Am79C972 PCnet-FAST+
119.It
120AMD Am79C973/Am79C975 PCnet-FAST III
121.It
122AMD Am79C976 PCnet-PRO
123.It
124AMD PCnet/Home HomePNA
125.It
126Allied-Telesis LA-PCI
127.It
128Contec C-NET(98)S (PC-98)
129.It
130NEC SV-98/2-B05, B06
131.El
132.Sh DIAGNOSTICS
133.Bl -diag
134.It "pcn%d: couldn't map ports/memory"
135A fatal initialization error has occurred.
136.It "pcn%d: couldn't map interrupt"
137A fatal initialization error has occurred.
138.It "pcn%d: watchdog timeout"
139The device has stopped responding to the network, or there is a problem with
140the network connection (e.g.\& a cable fault).
141.It "pcn%d: no memory for rx list"
142The driver failed to allocate an mbuf for the receiver ring.
143.It "pcn%d: no memory for tx list"
144The driver failed to allocate an mbuf for the transmitter ring when
145allocating a pad buffer or collapsing an mbuf chain into a cluster.
146.It "pcn%d: chip is in D3 power state -- setting to D0"
147This message applies only to adapters which support power
148management.
149Some operating systems place the controller in low power
150mode when shutting down, and some PCI BIOSes fail to bring the chip
151out of this state before configuring it.
152The controller loses all of
153its PCI configuration in the D3 state, so if the BIOS does not set
154it back to full power mode in time, it will not be able to configure it
155correctly.
156The driver tries to detect this condition and bring
157the adapter back to the D0 (full power) state, but this may not be
158enough to return the driver to a fully operational condition.
159If
160you see this message at boot time and the driver fails to attach
161the device as a network interface, you will have to perform a
162warm boot to have the device properly configured.
163.Pp
164Note that this condition only occurs when warm booting from another
165operating system.
166If you power down your system prior to booting
167.Fx ,
168the card should be configured correctly.
169.El
170.Sh SEE ALSO
171.Xr arp 4 ,
172.Xr miibus 4 ,
173.Xr netintro 4 ,
174.Xr ng_ether 4 ,
175.Xr ifconfig 8
176.Rs
177.%T AMD PCnet/FAST, PCnet/FAST+ and PCnet/Home datasheets
178.%O http://www.amd.com
179.Re
180.Sh HISTORY
181The
182.Nm
183device driver first appeared in
184.Fx 4.3 .
185.Sh AUTHORS
186The
187.Nm
188driver was written by
189.An Bill Paul Aq wpaul@osd.bsdi.com .
2.\" Copyright (c) 1997, 1998, 1999, 2000
3.\" Bill Paul <wpaul@osd.bsdi.com>. All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\" notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\" notice, this list of conditions and the following disclaimer in the
12.\" documentation and/or other materials provided with the distribution.
13.\" 3. All advertising materials mentioning features or use of this software
14.\" must display the following acknowledgement:
15.\" This product includes software developed by Bill Paul.
16.\" 4. Neither the name of the author nor the names of any co-contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
24.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
25.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
26.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
27.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
28.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
29.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
30.\" THE POSSIBILITY OF SUCH DAMAGE.
31.\"
32.\" $FreeBSD: head/share/man/man4/pcn.4 137881 2004-11-19 03:47:01Z obrien $
33.\"
34.Dd September 13, 2004
35.Dt PCN 4
36.Os
37.Sh NAME
38.Nm pcn
39.Nd "AMD PCnet/PCI Fast Ethernet device driver"
40.Sh SYNOPSIS
41.Cd "device miibus"
42.Cd "device pcn"
43.Sh DESCRIPTION
44The
45.Nm
46driver provides support for PCI Ethernet adapters and embedded
47controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III,
48PCnet/PRO and PCnet/Home Ethernet controller chips.
49Supported NIC's include the Allied Telesyn AT-2700 familly.
50.Pp
51The PCnet/PCI chips include a 100Mbps Ethernet MAC and support
52both a serial and MII-compliant transceiver interface.
53They use a bus master DMA and a scatter/gather descriptor scheme.
54The AMD chips provide a mechanism for zero-copy receive,
55providing good performance in server environments.
56Receive address filtering is provided using a single perfect filter entry
57for the station address and a 64-bit multicast hash table.
58.Pp
59The
60.Nm
61driver supports the following media types:
62.Pp
63.Bl -tag -width 10baseTXUTP
64.It autoselect
65Enable autoselection of the media type and options.
66The user can manually override
67the autoselected mode by adding media options to
68.Xr rc.conf 5 .
69.It 10baseT/UTP
70Set 10Mbps operation.
71The
72.Xr ifconfig 8
73.Cm mediaopt
74option can also be used to select either
75.Sq full-duplex
76or
77.Sq half-duplex
78modes.
79.It 100baseTX
80Set 100Mbps (Fast Ethernet) operation.
81The
82.Xr ifconfig 8
83.Cm mediaopt
84option can also be used to select either
85.Sq full-duplex
86or
87.Sq half-duplex
88modes.
89.El
90.Pp
91The
92.Nm
93driver supports the following media options:
94.Pp
95.Bl -tag -width full-duplex
96.It full-duplex
97Force full duplex operation
98.It half-duplex
99Force half duplex operation.
100.El
101.Pp
102For more information on configuring this device, see
103.Xr ifconfig 8 .
104.Sh HARDWARE
105The
106.Nm
107driver supports adapters and embedded controllers based on the AMD PCnet/FAST,
108PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home Fast Ethernet chips:
109.Pp
110.Bl -bullet -compact
111.It
112AMD Am53C974/Am79C970/Am79C974 PCnet-PCI
113.It
114AMD Am79C970A PCnet-PCI II
115.It
116AMD Am79C971 PCnet-FAST
117.It
118AMD Am79C972 PCnet-FAST+
119.It
120AMD Am79C973/Am79C975 PCnet-FAST III
121.It
122AMD Am79C976 PCnet-PRO
123.It
124AMD PCnet/Home HomePNA
125.It
126Allied-Telesis LA-PCI
127.It
128Contec C-NET(98)S (PC-98)
129.It
130NEC SV-98/2-B05, B06
131.El
132.Sh DIAGNOSTICS
133.Bl -diag
134.It "pcn%d: couldn't map ports/memory"
135A fatal initialization error has occurred.
136.It "pcn%d: couldn't map interrupt"
137A fatal initialization error has occurred.
138.It "pcn%d: watchdog timeout"
139The device has stopped responding to the network, or there is a problem with
140the network connection (e.g.\& a cable fault).
141.It "pcn%d: no memory for rx list"
142The driver failed to allocate an mbuf for the receiver ring.
143.It "pcn%d: no memory for tx list"
144The driver failed to allocate an mbuf for the transmitter ring when
145allocating a pad buffer or collapsing an mbuf chain into a cluster.
146.It "pcn%d: chip is in D3 power state -- setting to D0"
147This message applies only to adapters which support power
148management.
149Some operating systems place the controller in low power
150mode when shutting down, and some PCI BIOSes fail to bring the chip
151out of this state before configuring it.
152The controller loses all of
153its PCI configuration in the D3 state, so if the BIOS does not set
154it back to full power mode in time, it will not be able to configure it
155correctly.
156The driver tries to detect this condition and bring
157the adapter back to the D0 (full power) state, but this may not be
158enough to return the driver to a fully operational condition.
159If
160you see this message at boot time and the driver fails to attach
161the device as a network interface, you will have to perform a
162warm boot to have the device properly configured.
163.Pp
164Note that this condition only occurs when warm booting from another
165operating system.
166If you power down your system prior to booting
167.Fx ,
168the card should be configured correctly.
169.El
170.Sh SEE ALSO
171.Xr arp 4 ,
172.Xr miibus 4 ,
173.Xr netintro 4 ,
174.Xr ng_ether 4 ,
175.Xr ifconfig 8
176.Rs
177.%T AMD PCnet/FAST, PCnet/FAST+ and PCnet/Home datasheets
178.%O http://www.amd.com
179.Re
180.Sh HISTORY
181The
182.Nm
183device driver first appeared in
184.Fx 4.3 .
185.Sh AUTHORS
186The
187.Nm
188driver was written by
189.An Bill Paul Aq wpaul@osd.bsdi.com .