pcn(7d) [sunos man page]

pcn(7D) 							      Devices								   pcn(7D)

NAME

       pcn - AMD PCnet Ethernet controller device driver

SYNOPSIS

       /dev/pcn

DESCRIPTION

       The   pcn  Ethernet  driver  is a multi-threaded,  loadable, clonable driver for the  AMD PCnet family of Ethernet controllers that use the
       Generic	LAN Driver (GLD) facility to implement the required  STREAMS and Data Link Provider (see  dlpi(7P)) interfaces.

       This driver supports a number of integrated motherboards and  add-in adapters based on the AMD PCnet-ISA,  PCnet-PCI,  and   PCnet-32  con-
       troller chips. The  pcn driver functions include controller initialization, frame  transmit and receive, functional addresses,  promiscuous
       and multicast support, and error  recovery and reporting.

APPLICATION PROGRAMMING INTERFACE

       The cloning character-special device, /dev/pcn, is used to access all PCnet devices installed in the system.

pcn and DLPI
       The pcn driver uses the Solaris GLD module  which handles all the STREAMS and DLPI specific functions of the driver. It is a style  2  DLPI
       driver  and  therefore  supports only the connectionless mode of data transfer. Thus, a DLPI user should issue a DL_ATTACH_REQ primitive to
       select the device to be used. Valid DLPI primitives are defined in <sys/dlpi.h>. Refer to dlpi(7P) for more information.

       The device is initialized on the first attach and de-initialized (stopped) on the last detach.

       The values returned by the driver in the DL_INFO_ACK primitive in response to a DL_INFO_REQ from the user are:

	 o  Maximum SDU is 1500 (ETHERMTU - defined in <sys/ethernet.h>).

	 o  Minimum SDU is 0.

	 o  DLSAP address length is 8.

	 o  MAC type is DL_ETHER.

	 o  sap length value is -2, meaning the physical address component is followed immediately by a 2-byte	sap  component	within	the  DLSAP
	    address.

	 o  Service mode is DL_CLDLS.

	 o  No optional quality of service (QOS) support is included at present, accordingly, the QOS fields are 0.

	 o  Provider style is DL_STYLE2.

	 o  Version is DL_VERSION_2.

	 o  Broadcast address value is the Ethernet/IEEE broadcast address (FF:FF:FF:FF:FF:FF).

       Once in the DL_ATTACHED state, the user must send a DL_BIND_REQ to associate a particular Service Access Point (SAP) with the stream.

   Known Problems and Limitations
	 o  Occasional	data corruption has occurred when pcn and pcscsi drivers in HP Vectra XU 5/90 and Compaq Deskpro XL systems are used under
	    high network and  SCSI loads. These drivers do not perform well in a production server. A possible workaround is to disable  the   pcn
	    device with the system BIOS and use a separate add-in network interface.

	 o  The Solaris pcn driver does not support IRQ 4.

FILES

       /dev/pcn 	       Character special device

       /kernel/drv/pcn.conf    Configuration file

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Architecture		     |x86			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       attributes(5), standards(5), dlpi(7P), streamio(7I)

       Writing Device Drivers

       STREAMS Programming Guide

SunOS 5.10							    20 Oct 2000 							   pcn(7D)

PCN(4)							   BSD Kernel Interfaces Manual 						    PCN(4)

NAME

     pcn -- AMD PCnet/PCI Fast Ethernet device driver

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device miibus
	   device pcn

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   if_pcn_load="YES"

DESCRIPTION

     The pcn driver provides support for PCI Ethernet adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III,
     PCnet/PRO and PCnet/Home Ethernet controller chips.  Supported NIC's include the Allied Telesyn AT-2700 family.

     The PCnet/PCI chips include a 100Mbps Ethernet MAC and support both a serial and MII-compliant transceiver interface.  They use a bus master
     DMA and a scatter/gather descriptor scheme.  The AMD chips provide a mechanism for zero-copy receive, providing good performance in server
     environments.  Receive address filtering is provided using a single perfect filter entry for the station address and a 64-bit multicast hash
     table.

     The pcn driver supports the following media types:

     autoselect   Enable autoselection of the media type and options.  The user can manually override the autoselected mode by adding media
		  options to rc.conf(5).

     10baseT/UTP  Set 10Mbps operation.  The ifconfig(8) mediaopt option can also be used to select either 'full-duplex' or 'half-duplex' modes.

     100baseTX	  Set 100Mbps (Fast Ethernet) operation.  The ifconfig(8) mediaopt option can also be used to select either 'full-duplex' or
		  'half-duplex' modes.

     The pcn driver supports the following media options:

     full-duplex  Force full duplex operation

     half-duplex  Force half duplex operation.

     For more information on configuring this device, see ifconfig(8).

HARDWARE

     The pcn driver supports adapters and embedded controllers based on the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO and PCnet/Home
     Fast Ethernet chips:

     o	 AMD Am79C971 PCnet-FAST
     o	 AMD Am79C972 PCnet-FAST+
     o	 AMD Am79C973/Am79C975 PCnet-FAST III
     o	 AMD Am79C976 PCnet-PRO
     o	 AMD Am79C978 PCnet-Home
     o	 Allied-Telesis LA-PCI

DIAGNOSTICS

     pcn%d: couldn't map ports/memory  A fatal initialization error has occurred.

     pcn%d: couldn't map interrupt  A fatal initialization error has occurred.

     pcn%d: watchdog timeout  The device has stopped responding to the network, or there is a problem with the network connection (e.g. a cable
     fault).

     pcn%d: no memory for rx list  The driver failed to allocate an mbuf for the receiver ring.

     pcn%d: no memory for tx list  The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an
     mbuf chain into a cluster.

     pcn%d: chip is in D3 power state -- setting to D0	This message applies only to adapters which support power management.  Some operating sys-
     tems place the controller in low power mode when shutting down, and some PCI BIOSes fail to bring the chip out of this state before configur-
     ing 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 will not be able to configure it 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 you see this message at boot time and the driver
     fails to attach the device as a network interface, you will have to perform a warm boot to have the device properly configured.

     Note that this condition only occurs when warm booting from another operating system.  If you power down your system prior to booting
     FreeBSD, the card should be configured correctly.

SEE ALSO

     arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8)

     AMD PCnet/FAST, PCnet/FAST+ and PCnet/Home datasheets, http://www.amd.com.

HISTORY

     The pcn device driver first appeared in FreeBSD 4.3.

AUTHORS

     The pcn driver was written by Bill Paul <wpaul@osd.bsdi.com>.

BSD
								 January 31, 2006							       BSD