usr/share/man/cat4/vax/en.0

EN(4)             BSD Programmer's Manual (VAX Architecture)             EN(4)

N\bNA\bAM\bME\bE
     e\ben\bn - Xerox 3 Mb/s Ethernet interface

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     d\bde\bev\bvi\bic\bce\be e\ben\bn0\b0 a\bat\bt u\bub\bba\ba0\b0 c\bcs\bsr\br 1\b16\b61\b10\b00\b00\b0 v\bve\bec\bct\bto\bor\br e\ben\bnr\bri\bin\bnt\bt e\ben\bnx\bxi\bin\bnt\bt e\ben\bnc\bco\bol\bll\bli\bid\bde\be

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     The e\ben\bn interface provides access to a 3 Mb/s Ethernet network.  Due to
     limitations in the hardware, DMA transfers to and from the network must
     take place in the lower 64K bytes of the UNIBUS address space, and thus
     this must be among the first UNIBUS devices enabled after boot.

     Each of the host's network addresses is specified at boot time with an
     SIOCSIFADDR ioctl(2).  The station address is discovered by probing the
     on-board Ethernet address register, and is used to verify the protocol
     addresses.  No packets will be sent or accepted until a network address
     is supplied.

     The interface software implements an exponential backoff algorithm when
     notified of a collision on the cable.  This algorithm utilizes a 16-bit
     mask and the VAX-11's interval timer in calculating a series of random
     backoff values.  The algorithm is as follows:

           1.   Initialize the mask to be all 1's.

           2.   If the mask is zero, 16 retries have been made and we give up.

           3.   Shift the mask left one bit and formulate a backoff by masking
                the interval timer with the mask (this is actually the two's
                complement of the value).

           4.   Use the value calculated in step 3 to delay before retransmit-
                ting the packet.

     The interface handles both Internet and NS protocol families.  It normal-
     ly tries to use a ``trailer'' encapsulation to minimize copying data on
     input and output.  The use of trailers is negotiated with ARP. This nego-
     tiation may be disabled, on a per-interface basis, by setting the
     IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.

D\bDI\bIA\bAG\bGN\bNO\bOS\bST\bTI\bIC\bCS\bS
     e\ben\bn%\b%d\bd:\b: o\bou\but\btp\bpu\but\bt e\ber\brr\bro\bor\br.\b.  The hardware indicated an error on the previous
     transmission.

     e\ben\bn%\b%d\bd:\b: s\bse\ben\bnd\bd e\ber\brr\bro\bor\br.\b.  After 16 retransmissions using the exponential backoff
     algorithm described above, the packet was dropped.

     e\ben\bn%\b%d\bd:\b: i\bin\bnp\bpu\but\bt e\ber\brr\bro\bor\br.\b.  The hardware indicated an error in reading a packet
     off the cable.

     e\ben\bn%\b%d\bd:\b: c\bca\ban\bn'\b't\bt h\bha\ban\bnd\bdl\ble\be a\baf\bf%\b%d\bd.\b.  The interface was handed a message with ad-
     dresses formatted in an unsuitable address family; the packet was
     dropped.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     netintro(4),  inet(4)

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     The e\ben\bn driver appeared in 4.2BSD.

B\bBU\bUG\bGS\bS
     The device has insufficient buffering to handle back to back packets.
     This makes use in a production environment painful.

     The hardware does word at a time DMA without byte swapping.  To compen-
     sate, byte swapping of user data must either be done by the user or by
     the system.  A kludge to byte swap only IP packets is provided if the
     ENF_SWABIPS flag is defined in the driver and set at boot time with an
     SIOCSIFFLAGS ioctl.

4.2 Berkeley Distribution        June 5, 1993                                2