Network drivers package update - nd package version 8.0.6c KEYWORDS: uw uw7 714 600 openserver osr6 unix unixware broadcom bcme network ethernet adapter driver pci nic nd 8.0.6c RELEASE: UnixWare Release 7.1.4 OpenServer Release 6.0.0 PROBLEM: What has been updated/added in the 8.0.6c version of the nd package for OpenServer 6.0.0 and UnixWare 7.1.4? SOLUTION: The nd version 8.0.6c package provides fixes beyond the nd version 8.0.6b package. This can only be applied to an existing OpenServer 6.0.0 system with Maintenance Pack 2 applied or to a UnixWare 7.1.4 system with Maintenance Pack 3 applied. This image is available at the following URLs: ftp://ftp.sco.com/pub/unixware7/714/drivers ftp://ftp.sco.com/pub/openserver6/600/drivers Here is a complete list of NIC driver updates added in the nd version 8.0.6c package (beyond those available in the nd version 8.0.6b package): bcme - Broadcom BCM5700 NetXtreme nic driver Updated from version 7.5.22 to 8.2.11 bcme MODIFICATION HISTORY ************************* v8.2.11 (August 10, 2005) =========================== Fixes: ------------- 1) Problem : Driver fails SCO certification tests. Cause : Driver symbol does not conform to mandated symbol standards. Change : Rename symbol. Impact : None. v8.2.10 (August 02, 2005) =========================== Fixes: ------------- 1) Problem : (CQ10476) Tx statistic counters incorrect. Cause : Tx statistic counters are overflowing in hardware. Change : Reduce the statistic refresh interval. Impact : None. v8.2.9 (August 01, 2005) =========================== Fixes: ------------- 1) Problem : (CQ11321) 5700 fails to initialize. Cause : The 5700 DmaTest() function was incorrectly failing due to DMA timeout. Change : Change the code to return a success on DMA transation timeout. The data validation step that follows will catch any DMA errors. Impact : None. 2) Problem : (CQ13576) 5704S fails flow control test. Cause : The 5704 code was using the flow control definitions of a different register. Change : Use correct flow control definitions. Impact : None. v8.2.8 (July 22, 2005) =========================== Fixes: ------------- 1) Problem : (CQ13461) 5701 fails to receive traffic when configured to 10Mbps, half-duplex, link forced. Cause : The 5701 requires that the driver commit each direct register write by performing a dummy read to that same register. The compiler was optimizing the dummy read away, since the read value was not being used. Change : Force the compiler to keep the dummy read by adding the "volatile" keyword to the destination variable. Impact : None. v8.2.7 (July 20, 2005) =========================== Enhancements: ------------- 1) Change : Remove 5714 and 5715 support from the driver. Impact : None. v8.2.6 (July 14, 2005) =========================== Fixes: ------------- 1) Problem : Serdes 325i devices not recognized correctly. Cause : The driver's device list incorrectly linked HP's serdes 325i subsystem device ID to Broadcom's copper device ID. Change : Point HP's serdes 325i subsystem device ID to the correct Broadcom device ID. Impact : None. v8.2.5 (July 08, 2005) =========================== Fixes: ------------- 1) Problem : (CQ13319) Flow control fails to work in "auto" mode. Cause : The new flow control code requires that the link's duplex configuration be known. The existing code failed to determine this. Change : Determine the link's duplex setting before setting up the flow control. Impact : None. 2) Problem : (CQ12986) 5714 devices do not fall back to forced link if PCS_SYNCED is detected. Cause : Incorrect detection of PCS_SYNCED and RECEIVING_CFGS states. Change : Modified code to get these states from the PHY. Impact : None. v8.2.4 (June 20, 2005) =========================== Fixes: ------------- 1) Problem : (CQ13161) Certification test fails after performing the symbol checking stage. Cause : This bug is another instance of CQ12922 for OpenServer. When resetting the chip, the driver never reclaimed the packet resources. When the driver attempts to fill the buffer rings afterwards, there are no available resources. Change : Fix the ResetAdapter() logic to reclaim packet resources before resetting the chip. Impact : None. 2) Problem : (CQ12986) 5714 devices do not fall back to forced link if PCS_SYNCED is detected. Cause : Feature omission. Change : Added force link fallback code. Impact : None. v8.2.3 (June 13, 2005) =========================== Fixes: ------------- 1) Problem : (CQ13078) Jumbo frame size option missing on 5714 / 5715 devices. Cause : Missing configuration file option. Change : Add the configuration file option. Impact : None. 2) Problem : (CQ13057) Firmware version string missing product name on 5714 devices. Cause : The code that determines which version string extraction method incorrectly chooses the wrong method. Change : Correct the method classification code to include the 5714. Impact : None. 3) Problem : (CQ13022) 5703B1S never gets link. Cause : The firmware autonegotiation code was bouncing the link due to invalid flow control configuration. Change : Correct the flow control configuration code. Impact : None. 4) Problem : 5704S devices showing link up when link is still being negotiated. Cause : Code that forces link as a fallback does not detect valid link up conditions strictly enough. Change : Only fallback to force link up if autonegotiation is not in progress. Impact : None. v8.2.2 (May 6, 2005) =========================== Fixes: ------------- 1) Problem : (CQ12822) Flow control automation test fails. Cause : The code, which classified what flow control abilities the link partner was capable of, had recently been rewritten. In the case of unidirectional flow control, the new code accidentally classified the link partner's flow control capabilities to the wrong direction. Change : Correct the misclassification. Impact : None. Enhancements: ------------- 1) Change : Added support for new HP NC32Xi products. Impact : None. v8.2.1 (April 27, 2005) =========================== Enhancements: ------------- 1) Change : Added 5715X support into driver. Impact : None. v8.2.0 (April 22, 2005) =========================== Enhancements: ------------- 1) Change : Added 5714X / 5780X support into driver. Impact : None. v8.1.8 (April 5, 2005) =========================== Fixes: ------------- 1) Problem : (CQ12586) PCIE devices lock-up. Cause : Hardware posts infinite data credits during PCIE posted transactions. Change : Find all locations where the chipset might consolidate PCIE transactions and force them to be separate. Force setup code to read back all register writes. Impact : Minor performance impact on initialization. v8.1.7 (March 31, 2005) =========================== Fixes: ------------- 1) Problem : (CQ12151) Link negotiation fails when 5751 LOM is connected back-to-back with another device. Cause : Driver was mistakenly forced to use the MI interrupt mode. Change : Correct the code so that it uses the "link ready" mode. Impact : None. 2) Problem : (CQ12158) Driver incorrectly limits the number of receive rules available for the 5714 family of devices. Cause : The code which sets the limit on the number of receive rules incorrectly categorized 5714 family devices. Change : Correct the categorization code. Impact : None. 3) Problem : (CQ12156) ATI transmit timeout - "NETDEV WATCHDOG". Cause : The ATI chipset did not call the driver ISR after the ISR did not service an INTx interrupt. Change : The driver will check a register to determine if the INTx should be claimed if the status block has not been updated on ISR entry. Impact : This fix may improve system performance on some systems as it reduces the amount of spurious or unclaimed interrupts. Enhancements: ============= 1) Problem : Jumbo frame support on some systems caused device counters to increment CRC errors. Change : Set TX elasticity bit in PHY when using jumbo frames. Impact : None. 2) Problem : 5714 device support needs to be removed for the 8.1b driver release. Change : Removed 5714 family devices. Impact : None. v8.1.6 (March 24, 2005) =========================== Fixes: ------------- 1) Problem : (CQ12399) 5714 not detected. Cause : Missing configuration file. Change : Added configuration file. Impact : None. 2) Problem : (CQ12486) ndstat -l reports strange link speeds. Cause : Code that updates link speed incorrectly updated the field that reports the new speed. Change : Added code to update the link speed field. Impact : None. 3) Problem : (CQ12370) Systems with more than one adapter refuse to accept configuration changes. Cause : Configuration settings were not revisited when the device was reopened. Change : Added code to obtain the configuration settings every time the device is opened. Impact : None. Enhancements: ============= 1) Problem : Driver missing new HT-LE device IDs. Change : Added missing device IDs. Impact : None. v8.1.5 (March 2, 2005) =========================== Fixes: ------------- 1) Problem : (CQ12303) Firmware version not displayed for EEPROM devices. Cause : Code failed to put EEPROM NVRAMs on newer devices into the newer access mode. Change : Ensure EEPROMS on newer devices are accessed using the newer method. Impact : Firmware version now displays correctly. v8.1.4 (March 1, 2005) =========================== Fixes: ------------- 1) Problem : Driver crashes. Cause : Not enough memory allocated for device structures. Change : Fix code to allocate the appropriate amount of memory. Impact : None. 2) Problem : (CQ11893) ASF not supported. Cause : Driver detects ASF and refuses to load. Change : Add code to send ASF heartbeats. Impact : Driver and ASF can now coexist. v8.1.3 (March 1, 2005) =========================== Fixes: ------------- 1) Problem : (CQ12160) Capacitive coupling and preserve preemphasis settings may be set incorrectly. Cause : NVRAM configuration bits were not validated before being used. Change : Validate configuration bits before use. Impact : Configuration bits set as expected. 2) Problem : (CQ8960) ndstat does not show the correct link speed. Cause : Link speed is queried to soon on interface open. The status is never revisited. Change : With the use of a new primitive, the driver now sends a message to the upper layers whenever a link event happens. Impact : ndstat shows correct link speed. v8.1.2 (February 7, 2005) =========================== Enhancements: ------------- 1) Change : Added support for jumbo frames for 5714X and HT2000 devices. Impact : None. v8.1.1 (January 11, 2005) =========================== Enhancements: ------------- 1) Change : Added support for 5714X and HT2000 devices. Impact : None. v8.1.0 (January 07, 2005) =========================== Enhancements: ------------- 1) Change : Added support for Baxter devices. Impact : None. 2) Change : Updated copyright strings. Impact : None. v7.7.7 (December 14, 2004) =========================== Fixes: ------------- 1) Problem : (CQ11636) Device fails to get link when connection is forced to 10Mbps. Cause : Code which programs the LEDs programmed the wrong shadow register. Change : Changed code to program the correct shadow register. Impact : Device acquires link as expected. v7.7.6 (December 2, 2004) =========================== Enhancements: ------------- 1) Problem : (CQ11011) PLL clock unstable. Change : Set some hardware bits to stabilize the clock. Impact : Device works as expected. v7.7.5 (November 29, 2004) =========================== Fixes: ------------- 1) Problem : (CQ11448) 5704 LOM interfaces will not ping. Cause : Peer device can hold NVRAM lock, which prevents correct operation. Change : Release NVRAM lock after reset. Impact : Devices work as expected. v7.7.4 (November 29, 2004) =========================== Enhancements: ------------- 1) Change : Added support for more NVRAM types. Impact : More NVRAM types supported. v7.7.3 (November 9, 2004) ========================== Fixes: ------ 1) Problem : (CQ11088) Force the NC150T to autonegotiate its linkspeed and duplex settings. Cause : The 150T is a "LOM" connected to an onboard switch. Any other settings will cause a link failure. Change : Detect the NC150T and prevent changes to requested link speed / duplex and autoneg settings. Impact : The NC150T will autoneg or fail to link. v7.7.2 (November 8, 2004) ========================== Fixes: ------ 1) Problem : (CQ11219) Driver freezes machine under stress. Cause : Error in resource release code. Change : Changed code so that previously erroneous test will work. Impact : All resources can be released properly. Driver works as expected. 2) Problem : (CQ11270) Driver will not load on a BCM5700B2 Cause : BCM5700B2s do not have a valid EEPROM signature. Change : Changed code to prevent an error return when BCM5700 devices fail EEPROM signature check. Impact : BCM5700 devices work once again. 3) Problem : Firmware version number not displayed on Shasta devices. Cause : NVRAM on Shasta devices requires the "access enable" bit to be set before performing a read. Change : Set the access enable bit. Also averted an offset calculation on 5753 devices. Impact : Firmware version shod up on both devices. Enhancements: ------------- 1) Change : Added firmware version to banner string. Impact : It should be clearer which version of the firmware is on the device. 2) Problem : (CQ#11117) Preemphasis settings, set by the firmware, need to be preserved. Change : Added code to preserve preemphasis settings enabled by the bootcode, when requested. Impact : Better waveforms on particular serdes implementations. v7.7.1 (October 25, 2004) ========================== Fixes: ------ 1) Problem : Machine crashes when doing UDP performance testing. Cause : Streams queues were being corrupted when putbq() was being called incorrectly. Change : Recoded the tx path to remove the violation. Impact : Crashing condition removed. 2) Problem : 5753 series devices have a banner string identifying the devices as "Unknown". Cause : Omitted code to recognize the new devices. Change : New defines. Impact : New devices recognized. 3) Problem : Performance considerably slower on shasta devices. Cause : Shasta devices need to be programmed differently than other legacy devices. Change : Added new code to program shasta devices correctly. Impact : Performance back up to par. ------------------------------------------------------------------------- I. Installation Warning: Installing this driver overlays information in the /etc/inst/nd/mdi directory without backing up prior versions (if they existed). To restore prior versions, you must re-install the previous nd/driver package which the original driver came from. To install on any installed OpenServer 6/UnixWare 7 system, follow the below steps. 1. Become root and create a new directory by typing: $ su Password: # mkdir /tmp/nd # cd /tmp/nd 2. Download the nd.8.0.6c.image file to the newly created /tmp/nic directory on your machine. 3. Install the package on your machine: # pkgadd -d /tmp/nd/nd.8.0.6c.image nd 4. Use netcfg to optionally configure any new NIC cards newly supported in the nd driver package. 5. Reboot the system so any updates to the currently configured NIC drivers are completed. ------------------------------------------------------------------------ II. Software Notes This driver package has been tested with and is supported on: SCO UnixWare 7 Release 7.1.4 SCO OpenServer Release 6.0.0 HARDWARE: The following new cards supported in this version are: From the bcme 8.2.11 driver: Broadcom BCM5704S NetXtreme Gigabit Ethernet Broadcom BCM575XF NetXtreme Gigabit Ethernet Broadcom BCM5780 NetXtreme Gigabit Ethernet Broadcom BCM5781 NetXtreme Gigabit Ethernet HP NC320i Integrated Gigabit Server Adapter HP NC324i Integrated Dual Port PCI Express Gigabit Server Adapter HP NC325i Integrated Dual Port PCI Express Gigabit Server Adapter HP NC326i Integrated Dual Port PCI Express Gigabit Server Adapter