Conference helix::vxworks

279.0. "DEFPZ (FDDI) support for V5.2B" by HELIX::MIANO (My parents think I'm in college) Thu May 01 1997 20:56

    The DEFPZ network interface controller (FDDI) will be supported by
    VxWorks V5.2C. Because we've been alerted that this support is required
    by customers immediately, we've made a patch kit for VxWorks V5.2B.
    
    The kit will be distributed directly to customers via the Digital
    external web site and via the OEM internal web site. 
    
    There may be some delay getting it on the sites. Until it's there, we
    will provide it to anyone who requires it. Send mail to HELIX::REALTIME
    with a directory on your node we can copy it to. About 62K of disk
    space will be necessary. When it's available on the web, I'll post a
    reply to this note with the exact address.
    
    Attached, please find the kit's release notes.
    
    M
    
This is a device driver for the DEFPZ network interface controller. The
controller is unlike other network interface drivers in that it is based on
FDDI rather than Ethernet. 

This driver, as supplied, is intended to work with VxWorks for Alpha V5.2B. It
is an interim solution for those customers who would like to use the DEFPZ
support before it is officially released. Any V5.2B customer who requires this
support can be provided with this driver. It cannot be used on any version
except V5.2B. 

The V5.2C release of VxWorks will contain integrated support for the DEFPZ. At
that time, the V5.2B interim driver will be unsupported. Customers should
upgrade to V5.2C (when it is available) to get the production quality version
of the driver. 

The DEFPZ cannot be used as a boot device. It can be used as the primary
network interface after the system is booted. It can also be used as a
secondary network interface. That is, it can be used in addition to an existing
interface which may have been used to boot the system. 

The V5.2B interim driver support consists of the following two files: 

	        if_fwa.o		(the driver)
        	READMEFIRST 		(this text)

Follow these instructions to install the DEFPZ FDDI driver object code into the
V5.2B development tree driver library: 

        $cp if_fwa.o /usr/opt/VXW52B/lib/obj21064osfdrv/if_fwa.o
        $cd /usr/opt/VXW52B/lib
        $ar -r lib21064osfdrv.a ./obj21064osfdrv/if_fwa.o

The DEFPZ driver provides an external interface using the fwaattach() routine.
There is no separate "Init" routine. 

Routine Description:

 STATUS fwaattach
 (
     int         unit,
     int         bufNum,
     int         intVec
 )

Arguments:

 Unit   - Specifies the unit number.
 bufNum - Number of FDDI MTU (Maximum Transfer Unit) length buffers.
 	  Enter zero for defaults.
 intVec - Specifies the interrupt vector to be used by the driver to
	  service an interrupt from the FDDI board.  If an interrupt
	  vector is not specified (0), interrupt vector will be acquired
	  from the system.  This should always be the case for Alpha.

The VxWorks software initializes only the network controller from which it has
been booted. To add the DEFPZ interface, you need to attach the interface and
assign it a network address and network mask. 

To attach the interface, call the fwaattach() routine. The following example
shows how to call it using the VxWorks shell and with its default parameters: 

	-> fwaattach

You can also call fwaattach() from your application or from a suitable point in
usrConfig.c or usrNetwork.c. 

To set a subnet mask, call the ifMaskSet() routine. The following example uses
the shell to set the subnet mask to 255.255.255.0: 

	-> ifMaskSet "fwa0",0xffffff00

To set an internet address, call the ifAddrSet() routine. The following example
uses the shell to sets the internet address to 1.2.3.4: 

	-> ifAddrSet "fwa0","1.2.3.4"

Other systems which are connected directly or indirectly to your FDDI network
may require a routing table entry. On VxWorks use the routeAdd() function. On
UNIX systems, use the "route" command. 
    

    This driver now available on Digital's external web site:
    
    	http://www.digital.com/info/oem/products/vxworks/vxworks.htm