Release Notes for BSD 5.3 FDDI Driver ------------------------------------- Version : 1.5 Release date : 2000-08-02 1. Getting Started --------------- 1.1. Boot vxWorks. 1.2. Type 'ccfddiattach 0,0,0' to attach the driver. Verify that the fddi0 device exists by typing 'ifShow'. 1.3. Set the IP address using ifAddrSet. 1.4. Confirm the FDDI connection using ping. An example is shown below (NOTE: This example assumes there is already a NIC on the FDDI LAN which has been set up with an IP address of 10.0.0.1): -> ccfddiattach 0,0,0 value = 0 = 0x0 -> ifShow ppp (unit number 0): Flags: (0x71) UP POINT-TO-POINT ARP RUNNING Internet address: 172.16.0.2 Destination Internet address: 172.16.0.1 Netmask 0xffff0000 Subnetmask 0xffff0000 Metric is 0 Maximum Transfer Unit size is 1500 5 packets received; 5 packets sent 0 input errors; 0 output errors 0 collisions lo (unit number 0): Flags: (0x69) UP LOOPBACK ARP RUNNING Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000 Metric is 0 Maximum Transfer Unit size is 4096 0 packets received; 0 packets sent 0 input errors; 0 output errors 0 collisions fddi (unit number 0): Flags: (0x63) UP BROADCAST ARP RUNNING Netmask 0xffffffff Subnetmask 0xffffffff Ethernet address is 00:00:5a:45:f0:46 Metric is 0 Maximum Transfer Unit size is 4491 18 packets received; 0 packets sent 0 input errors; 0 output errors 0 collisions value = 18 = 0x12 -> ifAddrSet "fddi0","10.0.0.4" value = 0 = 0x0 -> ping "10.0.0.1" PING 10.0.0.1: 56 data bytes 64 bytes from 10.0.0.1: icmp_seq=0. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=1. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=2. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=3. time=0. ms 64 bytes from 10.0.0.1: icmp_seq=4. time=0. ms 2. Known Issues with the Current Release ------------------------------------- (* = outstanding issue) 2.1 Cannot boot over FDDI - fixed in b1.1. 2.2 * Support for one card only at this stage. 2.3 * FTP client & server has not been tested - client tested OK in b1.1. 2.4 Driver tends to fall over if changes are made to the ring while the driver is operational. The following message is printed: 0x1dd4d08 (tPingTx8): SMT PANIC: code: 510, msg: HWM: A protocol layer has tried to send a frame with aninvalid frame control - fixed in b1.1. 2.5 Receive throughput very low - fixed in b1.1. 2.6 ioctl functions have not been tested - SMT parameters will now be available via function call ccfddiGetStats() - tested OK in 1.3. 2.7 Driver occasionally reports 'uninitialized interrupt 7' - workaround in 1.0. 2.8 Driver allocates buffer memory from uncached area at 0x70000. This may conflict with other drivers / applications. A memory partition for this area should be allocated by the BSP - fixed in 1.0. 2.9 Machine hangs if no card installed (unconfirmed) - tested OK in 1.1. 3. Revision History ---------------- b1.0 - 1998-08-07 - ARK First release. b1.1 - 1998-08-21 - ARK Improved receive throughput. Increased receive buffers (fixes lost ping packets). Renamed driver entry points from skXxx to fdXxx (skattach is now fdattach). 1.0 - 1998-09-29 - ARK Renamed driver entry points (again) from fdXxx to ccfddiXxx (fdattach is now ccfddiattach). Driver now capable of operating with all cache options. Workaround for spurious interrupt 7 - use count_int7() to show interrupt 7 count. Improved kernel integration procedure (now using NETIF_USR_DECL and NETIF_USR_ENTRIES macros). Driver now allows number of transmit and receive buffers to be specified when attaching. 1.1 - 1998-11-20 - ARK Driver tested OK with no card installed. 1.2 - 1998-11-24 - ARK Added ccfddiSuspendDriver and ccfddiResumeDriver functions to allow BIT software to manage driver. b1.3 - 1998-12-22 - ARK SMT 7.3 parameters are now available via ccfddiGetStats() & ccfddiShowStats(). 1.4 - 1999-02-15 - ARK Removed debug symbols. 1.5 - 2000-08-02 - GJK Increased rx & tx buffers to 30 and 40 + Added support for Radstone PPC1a