cm(4) [debian man page]

CM(4)							   BSD Kernel Interfaces Manual 						     CM(4)

NAME

     cm -- SMC Arcnet Ethernet device driver

SYNOPSIS

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

	   device isa
	   device cm

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

	   if_cm_load="YES"

DESCRIPTION

     The cm driver provides support for the Arcnet ISA network adapters.

     This driver also has quirks preset in the device.hints(5) file for card detection.

HARDWARE

     The cm driver supports the following card models:

     o	 SMC90c26
     o	 SMC90c56
     o	 SMC90c66 in '56 compatibility mode.

IMPLEMENTATION NOTES

     When the NOARP flag is set on the cm interface, it does not employ the address resolution protocol described in arp(4) to dynamically map
     between Internet and Ethernet addresses on the local network.  Instead it uses the least significant 8 bits of the IP address as the hardware
     address like described in RFC 1051 and RFC 1201.

     With the IFF_LINK0 flag cleared IP/ARP/RARP encoding is done according to RFC 1201 that is, with Packet Header Definition Standard header and
     packet type 212 / 213.  The MTU is normally 1500.	The IFF_LINK0 flag is cleared by default.

     With the IFF_LINK0 flag set, IP and ARP encoding is done according to the deprecated RFC 1051 encoding, that is with simple header, packet
     type 240 / 241, and the MTU is 507.

     When switching between the two modes, use
	   ifconfig interfacename down up
     to switch the MTU.

DIAGNOSTICS

     The following driver specific error messages may be reported:

     reset: card reset, link addr = 0x%02x (cm%d)  The card is being reset and a new link address assigned.

     srint: restarted rx on buf cm%d  The rx buffer has been emptied and will be reset.

SEE ALSO

     netintro(4), watchdog(4), device.hints(5), ifconfig(8), watchdog(8)

HISTORY

     The cm device was ported from NetBSD by Max Khon <fjoe@FreeBSD.org> and first appeared in FreeBSD 4.6.  This manual page first appeared in
     FreeBSD 5.3.

AUTHORS

     This manual page was written by Tom Rhodes <trhodes@FreeBSD.org>.	The IMPLEMENTATION NOTES section was submitted by
     Max Khon <fjoe@FreeBSD.org> and originated from NetBSD.

BUGS

     The cm driver code could do with a bit of improvement, it would be nice if some one could come along and take care of this.

     The IMPLEMENTATION NOTES section is specific to all Arcnet devices (see sys/net/if_arcsubr.c) and should be moved to a more generic location.

BSD
								   July 16, 2005							       BSD

Check Out this Related Man Page

TX(4)							   BSD Kernel Interfaces Manual 						     TX(4)

NAME

     tx -- SMC 83c17x Fast Ethernet device driver

SYNOPSIS

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

	   device miibus
	   device tx

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

	   if_tx_load="YES"

DESCRIPTION

     The tx driver provides support for the Ethernet adapters based on the SMC 83c17x (EPIC) chips.  These are mostly SMC 9432 series cards.

     The tx driver supports the following media types (depending on card's capabilities):

     autoselect   Enable autonegotiation (default).

     100baseFX	  Set 100Mbps (Fast Ethernet) fiber optic operation.

     100baseTX	  Set 100Mbps (Fast Ethernet) twisted pair operation.

     10baseT/UTP  Set 10Mbps on 10baseT port.

     10base2/BNC  Set 10Mbps on 10base2 port.

     The tx driver supports the following media options:

     full-duplex  Set full-duplex operation.

     The tx driver supports oversized Ethernet packets (up to 1600 bytes).  Refer to the ifconfig(8) man page on setting the interface's MTU.

     The old ``ifconfig tx0 linkN'' method of configuration is not supported.

   VLAN (IEEE 802.1Q) support
     The tx driver supports the VLAN operation (using vlan(4) interfaces) without decreasing the MTU on the vlan(4) interfaces.

DIAGNOSTICS

     tx%d: device timeout %d packets  The device stops responding.  Device and driver reset follows this error.

     tx%d: PCI fatal error occurred (%s)  One of following errors occurred: PCI Target Abort, PCI Master Abort, Data Parity Error or Address Par-
     ity Error.  Device and driver reset follows this error.

     tx%d: cannot allocate mbuf header/cluster	Cannot allocate memory for received packet.  Packet thrown away.

     tx%d: can't stop %s DMA  While resetting, the driver failed to stop the device correctly.

SEE ALSO

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

BUGS

     The auto-negotiation does not work very well.

BSD
								   July 16, 2005							       BSD

Linux and UNIX Man Pages

cm(4) [debian man page]

Check Out this Related Man Page