Release Notes Broadcom bnx2 Linux Driver Version 1.4.43b 06/26/2006 Broadcom Corporation 16215 Alton Parkway, Irvine, CA 92619-7013 Copyright (c) 2004, 2005, 2006 Broadcom Corporation All rights reserved v1.4.43b (June 26, 2006) ======================= Enhancement: ------------ 1. Change: (CQ25508) Use DRV_MSG_CODE_UNLOAD_LNK_DN message on 5708 B1 and older chips so that the link will turn off after ifdown. Impact: None. v1.4.42b (June 2, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL cannot be enabled on 5708 B2. Cause: Hardware limitation in previous 5708 versions required driver to always disable driver WoL on 5708. Change: With the issue fixed in B2, the driver was changed to allow 5708 B2 and above to support driver WoL. Impact: None. 2. Problem: (CQ21779) Driver does not report dropped receive packets. Cause: Packets dropped by firmware are reported in a scratch pad location in memory separate from other counters. Change: Added code to report this firmware counter. Impact: None. Enhancements: ------------- 1. Change: (CQ24690) Allow driver to be compiled for non-running kernels. Impact: None. v1.4.41b (May 17, 2006) ======================= Fixes: ------ 1. Problem: Driver writes wrong data to non-buffered flash. Cause: Bug in driver causing the unchanged portion of the page to be corrupted. Change: Fixed bug. Impact: None. v1.4.40b (April 17, 2006) ========================= Enhancements: ------------- 1. Change: Combine 2 small memory allocations into 1. Impact: None. 2. Change: Separate tx consumer and producer entries into separate cache lines for better performance. Impact: None. 3. Change: Compress firmware data to reduce driver size. Impact: Driver now requires zib_inflate library which should be available on most vendor kernels. v1.4.39b (Mar. 10, 2006) ======================= Fixes: ------ 1. Problem: (CQ23181) Driver loses track of link changes in some cases. Cause: In some cases, the status block gets a link change indication that contradicts with the MII link status. This is due to transient link signals during link changes. Change: Add coalesce_now at the end of link change interrupt to flush out the transient behavior. Impact: None. 2. Problem: 5708 only supports 40-bit DMA addresses. Cause: Limitation of the built-in PCIE-to-PCIX bridge. Change: Add workaround code to make sure all DMA addresses are less than 40 bits. Impact: Some minor impact on performance on some 64-bits systems. There should be practically no performance impact on i386 and x86_64 systems. 3. Problem: "Copyright" deprecated in RPM spec file. Change: Changed to "License". Impact: Should be none on the distributions that we support. v1.4.38b (Feb. 10, 2006) ======================= Fixes: ------ 1. Problem: Setting rx ring size to 255 causes memory allocation errors. Cause: Multiple bugs that do not handle the full ring properly. Change: Fixed all bugs related to full ring handling and changed maximum ring size from 4080 to 1020 after discussion with Dave Miller. Impact: Maximum rx ring size is now smaller. 2. Problem: Compile warnings and panic on IA64. Cause: not included. Change: Added include . Impact: None. v1.4.36b (Jan. 19, 2006) ======================= Version number update. v1.3.36 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22827) bnx2 does not compile on 2.6.6 and earlier kernels. Cause: Introduced bug while fixing CQ22666. Change: Fix compatibility code. Impact: None. 2. Problem: (CQ22823) bnx2 reports extra .5 at the end of firmware version string. Change: Skip the last digit in the firmware version string. Impact: None. 3. Problem: (CQ22585) WoL still does not work on 5708. Cause: New WoL mechanism introduced in 1.3.34 has a flaw. Change: Removed the workaround code and disabled WoL support on 5708. During shutdown and suspend, the driver will shutdown the device and WoL will be setup by the bootcode according to the nvram's out-of-box WoL setting. Impact: 5708 will not support driver-initiated (ethtool-intiated) WoL. v1.3.35 (Jan. 17, 2006) ======================= Fixes: ------ 1. Problem: (CQ22666) bnx2 driver does not compile on RHEL3 U7. Cause: if_mii() back-ported to RHEL3 U7. Change: Adjusted the compatibility code. Impact: None. 2. Problem: (CQ22718) UMP connection is lost after enabling WoL. Cause: FORCE LINK was mistakenly set during WoL setup. Change: Do not set FORCE LINK. Impact: None. v1.3.34 (Jan. 13, 2006) ======================= Fixes: ------ 1. Problem: (CQ22585) WoL does not work on 5708. Cause: Internal bridge not in proper PME state. Change: Added new firmware message to allow bootcode to help set up WoL. Impact: None. Enhancements: ------------- 1. Change: Added compile option to include crc32 function for RH2.4 boot kernels. Impact: None. 2. Change: Updated TSO firmware to handle ECN. Impact: None. v1.3.33 (Dec. 12, 2005) ======================= Enhancements: ------------- 1. Change: Increased firmware hand-shake timeout from 50 msec to 100 msec. Also changed the delay from busy-wait udelay to non-busy-wait msleep. Impact: None. 2. Change: Added code to read nvram size from shared memory if available. Otherwise, the size will come from the flash table which only gives the smallest size for that type of flash. Impact: None. 3. Change: Added workaround to issue 2 separate IOs for interrupt acknowledgement. The workaround is only used for INTA (non-MSI) interrupts. Impact: Slightly higher overhead for INTA interrupts. v1.3.32 (Dec. 01, 2005) ======================= Enhancements: ------------- 1. Change: Added PHY loopback to the loopback selftest. Impact: None. 2. Change: (CQ21810) Added ethtool -d register dump. Impact: None. 3. Change: Reduce the number of registers tested in selftest to make the driver smaller. Impact: None. 4. Change: Increased maximum rx ring size to 4080. Impact: None. 5. Change: Changed rx checksum logic for better reliability. Impact: None. 6. Change: Added 5708 B1 workarounds. Impact: None. v1.3.31 (Nov. 18, 2005) ======================= Fixes: ------ 1. Problem: (CQTO2080) Cannot pass traffic during 2nd ifup if IPMI is enabled. Cause: A flaw in driver/firmware handshake. Change: Changed driver/firmware handshake by doing WAIT0 first before writing the first signature. Impact: None. 2. Problem: (CQTO2056) VLAN-tagged IPMI traffic fails after driver is loaded. Cause: Driver configures the NIC to keep the VLAN tag by default, causing VLAN-tagged IPMI traffic to fail. Change: Changed driver to always strip VLAN tags if IPMI is enabled. Impact: VLAN will always be stripped when IPMI is enabled. This may affect some applications that rely on raw VLAN packets. Enhancements: ------------- 1. Change: Sync'ed up with latest upstream bnx2. v1.3.29 (Oct. 6, 2005) ======================= Fixes: ------ 1. Problem: (CQTO1929) Traffic stops when MTU is greater than 1500 with TSO enabled. Cause: TSO firmware bug. Change: Updated to latest firmware. Impact: None. v1.3.28 (Sep. 29, 2005) ======================= Fixes: ------ 1. Problem: (CQTO1875) Traffic stops when running Nettack with TSO turned on. Cause: TSO firmware bug. Change: Updated to latest firmware. Impact: None. 2. Problem: (CQTO1575) ethtool -S shows non-zero rx_error_bytes. Cause: Hardware errata. Change: Ignore this counter and always report zero. Impact: None. v1.3.27 (Sep. 21, 2005) ======================= Enhancements: ------------- 1. Change: Enabled ethernet@wirespeed on copper devices. Impact: None. 2. Change: Enabled customized pre-emphasis and other serdes control settings on 5708S backplane devices. A special PHY register will be programmed according to the NVRAM value. Impact: None. 3. Change: Modified Makefile to check for the source symbolic link in the kbuild environment. Impact: None. 4. Change: Improved NAPI poll processing so that all events will be processed before interrupts are re-enabled. This will reduce the number of unnecessary interrupts. Impact: None. 5. Change: Add support for ETHTOOL_GPERMADDR (from John Linville) Impact: None. Fixes: ------ 1. Problem: Bug in irq handler causing extra register read. Cause: Bug in bnx2_interrupt() reading BNX2_PCICFG_MISC_STATUS register when it is not necessary. Change: Fixed the logic bug and added prefetch of status block in msi handler. Impact: None. v1.3.25 (Aug. 22, 2005) ======================= Fixes: ------ 1. Problem: Ethtool register and memory tests fail on 5708. Cause: Some code was not merged properly many versions ago. Change: Merged in properly code. Impact: None. Enhancements: ------------- 1. Change: Slow down flash clock speeds Impact: None. 2. Change: Code re-sync'ed with upstream driver. Impact: None. v1.3.24 (Aug. 16, 2005) ======================= Enhancements: ------------- 1. Change: Changed all spin_lock_irqsave locks to spin_lock_bh for better overall system performance. All code requiring spin_lock runs in BH or user context. Impact: None. 2. Change: Removed atomic operations in the transmit fast path. Code should run a bit faster as atomic operations can be quite slow. Impact: None. v1.3.23 (Aug. 10, 2005) ======================= Enhancements: ------------- 1. Change: Added reporting of link speed to firmware. Impact: None. 2. Change: Added shared memory base look-up. Impact: None. 3. Change: Possible sparse fixes (from Peter Hagervall) - use C99 struct initializers - make a few arrays and structs static - remove a few uses of literal 0 as NULL pointer - use convenience function instead of cast+dereference in bnx2_ioctl() - remove superfluous casts to u8 * in calls to readl/writel Impact: None. 4. Change: Updated documentation with the crc32 library requirement and other minor updates. Impact: None. v1.3.22 (July 25, 2005) ======================= Enhancements: ------------- 1. Change: Added check for default link speed setting in shared memory. This allows some blade servers that don't support autoneg to default to forced speed to speed up link-up time. Impact: None. 2. Change: Changed timer code to speed up the timer after serdes autoneg. This speeds up the time for parallel detection when the link partner does not autoneg. After autoneg or parallel detction completes, timer goes back to normal 1 HZ interval. With the new scheme, link should be detected up using parallel detection in less than 0.7 seconds. Autoneg normally completes in 120 msec exchanging base pages and 3 next pages. Impact: None. v1.3.21 (July 21, 2005) ======================= Enhancements: ------------- 1. Change: Updated firmware to properly handle TSO packets with ECN bits set. Impact: None. 2. Change: Updated to latest rxp firmware. Impact: None. 3. Change: Added check for the 2.5G capability in shared memory. Impact: None. 4. Change: Expanded nvram support for 5708. Impact: None. Fixes: ------ 1. Problem: (CQTO1511) Downing a team of bnx2 adapters causes hang. Cause: Deadlock when the second adapter's close routine calls flush_scheduled_work() because the linkwatch_event is scheduled on the work queue when the first adapter is closed. The linkwatch_event will try to get the rtnl_lock which is already held by the bnx2_close routine. Change: Fixed by not calling flush_scheduled_work(). Instead, use a flag to indicate work is pending and wait until the flag is cleared. Impact: None. 2. Problem: (CQTO1439) ethtool -S on 5708 causes oops. Cause: A pointer is not initialized if the device is 5708. Change: Added proper initialization. Impact: None. 3. Problem: Some error counters are mis-reporting. Cause: The workaround for the hw errata is not applied properly on the chips with the errata. Change: Added proper checks for the workaround. Impact: None. 4. Problem: High BER on 5708 SerDes. Cause: hardware errata. Change: Added workaround for 5708 A0 and B0. Impact: None. v1.3.19 (May 27, 2005) ======================= Enhancements: ------------- 1. Change: Merged 5708 code with the latest 1.1.19. Impact: None. Fixes: ------ 1. Problem: (CQTO1260) 5708S does not link at 1000Mbps when forced. It links at 2500Mbps when connected back-to-back with another 5708S. Cause: 2.5G bit is still turned on. Change: Fixed by turning off 2.5G when the speed is forced. Impact: None. v1.1.19 (May 26, 2005) ======================= Enhancements: ------------- 1. Change: Made significant changes to merge into the kernel. Among them, consolidate all source files into bnx2.[ch] and bnx2_fw.h, change structure style register definitions to offset based. Impact: None. Fixes: ------ 1. Problem: Excessive stack usage. Cause: Use of local variable array. Change: Fix excessive stack usage in bnx2_alloc_bad_rbuf() by replacing local variable array with kmalloc array. Also changed function to return error code, and changed some of the callers to check for the return code. Impact: None. 2. Problem: Bug in receive checksum. Cause: Software bug. Change: Fix bug in rx checksum by indicating CHECKSUM_UNNECESSARY only when the hw calculated checksum is 0xffff. Impact: None. 3. Problem: Excessive busy loop. Cause: Software bug. Change: Replaced one excessive udelay of 15msec with msleep since the calling context is always process. Impact: None. 4. Problem: Need to call flush_scheduled_work() and bnx2_netif_stop(). Cause: Bug in bnx2_close(). Change: Fix bug in bnx2_close() by calling flush_scheduled_work() since we are using a work queue in netdev watchdog. Also added bnx2_netif_stop() call in bnx2_close(). Impact: None. 5. Problem: Some symbols do not have bnx2 prefix and are not static. Change: Add bnx2_ prefix to some remaining names and mark some remaining names static. Impact: None. v1.1.17 (Apr. 7, 2005) ======================= Fixes: ------ 1. Problem: Driver does not compile on 2.6.12 kernel. Cause: pci_dev->slot_name has been deprecated. Change: replaced with pci_name. Impact: None. All kernels supported by bnx2 including 2.4.21-*EL have pci_name defined. v1.1.16 (Mar. 16, 2005) ======================= Fixes: ------ 1. Problem: (CQTO936 & 1004) Tx carrier and rx_byte_errors reported during normal operations. Cause: 5706 hardware errata on these 2 statistics counters. Change: Modified driver to skip these 2 counters. Impact: These 2 counters will always report 0 and not the true statistics. v1.3.15 (Mar. 11, 2005) ====================== Enhancements: ------------- 1. Change: Added SGMII 10/100/1000 Mbps and fiber mode 1000/2500 Mbps support. Impact: None. v1.1.15 (Mar. 09, 2005) ======================= Enhancements: ------------- 1. Change: Added code to program proper phy settings for jumbo frames on copper and serdes devices. Impact: None. 2. Change: Changed INTx ISR to handle a valid case where INTx arrives before status block update. Impact: None. 3. Change: Added a separate ISR for MSI to handle subtle differences between INTx and MSI. Impact: None. v1.1.14 (Mar. 03, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work on latest RH3EL errata kernel. Cause: #define RED_HAT_LINUX_KERNEL removed from kernel include files, causing netdump poll function to be compiled wrong for RH kernels. Change: Changed Makefile to workaround the problem. Impact: None. v1.1.12 (Feb. 25, 2005) ====================== Fixes: ------ 1. Problem: (CQTO1062) Driver allows ethtool to set illegal speed/duplex on fiber cards. Cause: Missing checks for the case where autoneg is off. Change: Added proper checks. Impact: No. v1.1.11 (Feb. 18, 2005) ====================== Enhancements: ------------- 1. Change: (CQTO901) Added bnx2(4) man page. Impact: None. v1.1.10 (Feb. 16, 2005) ====================== Fixes: ------ 1. Problem: Wrong device ID in pci_dev_id table. Change: Fixed ID. Impact: None. v1.1.9 (Feb. 10, 2005) ====================== Fixes: ------ 1. Problem: (CQTO771) Driver fails to compile on RHEL3 update 4. Cause: The RH kernel has back-ported some netif functions not found in the same vanilla kernel version. Duplicate function names are defined. Change: Added intelligence in Makefile to detect such conditions and change the CFLAGS accordingly. Impact: None. 2. Problem: (CQTO1017) Driver allows 1000 half duplex autoneg off. Cause: Missing validity check. Change: Added check. Impact: None. Enhancements: ------------- 1. Change: The code to handle tx queue full condition was redone to properly handle all boundary and race conditions. Impact: Minimum tx ring size is now MAX_SKB_FRAGS+1. 2. Change: Tx timeout code was changed to work queue context. This allows netif to be shutdown gracefully before chip reset. Impact: None. 3. Change: Added memory barriers to ISR and NAPI poll for correctness. Impact: None. v1.1.8 (Feb. 01, 2005) ====================== Fixes: ------ 1. Problem: (CQTO969) No interupts on a system that does not support MSI. Cause: On this system, the MSI generated in the MSI test terminates with Master Abort which is a fatal condition for the chip. Change: A chip reset is added when MSI test fails to bring the chip back to normal operations again (in INTx mode). Impact: None. Enhancements: ------------- 1. Change: Removed register 0x84 from the ethtool register test. This is an interrupt control register that should not be touched to prevent unwanted interrupts. Impact: None. v1.1.7 (Jan. 28, 2005) ====================== Enhancements: ------------- 1. Change: Added interrupt test when MSI is enabled. If MSI test fails, driver will fallback to INTx mode. Impact: None. 2. Change: Added test for certain chipsets where MSI is known to fail, and disable MSI unconditionally when such chipsets are found. Impact: None. 3. Change: Removed support for 1000 Mbps half duplex. Impact: 1000 Mbps half duplex will no longer work. v1.1.6 (Jan. 26, 2005) ====================== Fixes: ------ 1. Problem: (CQTO940) MTU size not set properly when device is down. Cause: bnx2_change_mtu only handled the "up" case. Change: Simple fix to handle the "down" case as well. Impact: None 2. Problem: (CQTO926) 5706S does not autoneg properly after the tx cable is pulled. Cause: If the link partner is autonegotiating, autoneg will fail when the tx cable is pulled. The software will turn off autoneg seeing that the rx cable is still attached with SIGNAL_DETECT. When the tx cable is re-attached, autoneg is still off and the link partner will not establish link. Change: Added code to poll another PHY register to check if configs are received when autoneg is disabled. Impact: None Enhancements: ------------- 1. Change: Added OEM product name strings. Impact: None. v1.1.5 (Jan. 25, 2005) ====================== Fixes: ------ 1. Problem: PCI-X bus speed may not be detected correctly by the driver, causing failure because certain register settings are done based on bus speed. Cause: hardware problem. Change: Use a different register to detect PCI-X speed. Impact: None. v1.1.4 (Jan. 17, 2005) ====================== Fixes: ------ 1. Problem: 5706S does not reliably detect link up or down. Cause: hardware problem. Change: Enabled hardware workaround which is effective in A2 and newer chips only. Impact: None. v1.1.3 (Jan. 13, 2005) ====================== Fixes: ------ 1. Problem: netdump does not work. Cause: poll_controller routine does not work in NAPI mode. Change: Fixed poll_controller routine for NAPI mode. Impact: None. Enhancements: ------------- 1. Change: Added the new mmiowb macro which is used mainly in NUMA machines to guarantee PCI ordering. Impact: None. 2. Change: Added OEM product name strings. Impact: None. 3. Change: Changed ONE_TDMA workaround on systems with P64H bridge to PING_PONG_DMA on all systems using PCI. Impact: Better performance and better compatibility on all PCI systems. 4. Change: Added "disable_msi" parameter to allow disabling MSI. Impact: None. 5. Change: Reduced default tx coalescing parameters for better tx only performance such as ttcp. Impact: None. 6. Change: Changed NIC detection console message to display more information. Impact: None. 7. Change: Cleaned up some Linux .h files that are not needed. Impact: None. 8. Change: Cleaned up the nvram routines. Impact: None. v1.1.2 (Nov. 11, 2004) ====================== Fixes: ------ 1. Problem: Unable to load the driver on more than 2 or 3 devices. Cause: Default register space is too big. System fails to map the register space on the 3rd or 4th device. Change: Changed driver to map a smaller register space as the higher registers are not needed for standard operations. Impact: None. v1.1.1 (Nov. 9, 2004) ====================== Fixes: ------ 1. Problem: (CQTO656) One remaining ethtool parameter can be set out of range. Cause: Wrong upper bounds in code. Change: Fixed upper bound. Impact: None. 1. Problem: 5706 A1 cannot be run on a PCI bus. Cause: Hardware errata. Change: Added workaround to detect 5706 A1 on PCI bus and abort. Impact: Driver will not load 5706 A1 on PCI bus. v1.1.0 (Oct. 29, 2004) ====================== Fixes: ------ 1. Problem: (CQTO663) No link on fiber NIC set to autoneg when the link partner is set to forced speed. Cause: No code to handle this case. Change: Added code to check SIGNAL DETECT when autoneg fails, and turn off autoneg when appropriate. Also added code to force a link down when speed settings are changed. Impact: None. 2. Problem: (CQTO649) ifconfig up/down can cause system to hang on 2.6 kernels using mmconfig. Cause: Dummy read in the kernel's pci_mmcfg_write routine may cause system to hang during D3hot -> D0 transition. The PLL may lose lock during the internal D0 transition chip reset and cause the dummy read to hang. Change: The PLL problem will be fixed in A2. Meanwhile, the driver is changed to go into D3hot only if wol is enabled. Impact: Minor impact in increased power consumption when the driver is shutdown with wol disabled. 3. Change: Changed to use pci_get_device as pci_find_device will be deprecated soon. Impact: None. 4. Problem: (CQTO656) Some ethtool parameters can be set out of range. Cause: Wrong upper bounds in code or documentation. Change: Fixed code and documentation. Impact: None. v1.0.15 (Oct. 15, 2004) ====================== Fixes: ------ 1. Problem: (CQTO644) Data corruption when sending FTP traffic on Dell Precision 530MT. Cause: PCI bridge errata. Change: Added code to enable ONE_TDMA workaround when P64H PCI bridge is detected. Impact: Slower tx performance on systems using P64H bridge. 2. Problem: (CQTO643) Driver allows MTU to be set up to 9004. Cause: Driver used the wrong upper bound limit. Change: Fixed the upper bound. Impact: None. 3. Problem: Driver does not support forced speed on 5706S. Cause: Missing software logic. Change: Added code to support forced 1000 Full and Half duplex. Impact: None. 4. Change: Added workaround to disable PERR generation on 5706 A1 when it is in PCI 64-bit slot. Impact: None. v1.0.14 (Oct. 05, 2004) ====================== Fixes: ------ 1. Problem: Driver load/unload hangs on some machines. Cause: Transition delay required during D3hot -> D0 transition. Change: Added necessary delay. Impact: None. v1.0.12 (Oct. 04, 2004) ====================== Fixes: ------ 1. Problem: (CQTO609) New flow control parameter does not take effect until ifdown/ifup or link down/up. Cause: New flow control settings are only configured during link up. The driver did not check flow control advertisement changes and therefore no re-negotiation and no link down. Change: Fixed logic so that link will always go down whenever there is a change a flow control advertisement. Impact: None. 2. Problem: (CQTO612) VLAN packet reception not working. Cause: VLAN #define not setup properly. Change: Fixed #define for VLAN. Impact: None. 3. Problem: (CQTO628) WoL not functioning correctly. Cause: Multiple problems in the WoL code. Change: Fixed by: 1. using sort mode. 2. setting up mac address correctly. Impact: None. Enhancements: ------------- 1. Change: Added support for non-dword and non-aligned write access to eeprom, allowing ethtool -E to work. Impact: None. v1.0.11 (Sep. 24, 2004) ====================== Fixes: ------ 1. Problem: (CQTO600) Kernel panic when attempting to ftp on Fedora kernel. Cause: skbuffs are 4-byte aligned on Fedora, causing the rx headers to be misaligned. skbuffs are 16-byte aligned on other standard kernels. Change: Removed any assumptions about skbuff alignment and added code to align all rx skbuffs to 8-byte boundaries. Impact: None. Enhancements: ------------- 1. Change: Added netif_carrier_off to Driver init code so that the initial link state is off. Impact: None. v1.0.10 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: (CQTO599) Driver fails to compile on RH 3.0ES. Cause: Bug in poll_bcm5706 where bp is referenced without being defined. Change: Fixed the minor bug. Impact: None. v1.0.9 (Sep. 23, 2004) ====================== Fixes: ------ 1. Problem: Jumbo frames not working reliably. Cause: Bug in bcm5706_reuse_rx_skb. Change: Fixed the bug so that the host address is properly copied from one BD to the other. Impact: None. Enhancements: ------------- 1. Change: Change the locking scheme for more reliable open/close/ioctl operations where the spinlock is needed. Impact: None. 2. Change: Added minimum MTU size check for MTU changes. Impact: None. v1.0.8 (Sep. 20, 2004) ====================== Fixes: ------ 1. Problem: (CQTO561) Kernel panic on RH30EL after repeated driver load/unload. Cause: Occasionally, the system is unable to map device registers, causing subsequent register access to fail. Change: Added check for the return value from ioremap, and exit gracefully if it fails. Impact: None. 2. Problem: (CQTO574) NETDEV WATCHDOG when running 5706 A1 on PCIX 133MHz slot. Cause: Some hw register setup required for 133 Mhz. Change: Added the register setup code. Impact: None. 3. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa when the link partner is also using forced speed. Cause: Delay not long enough for the link to go down. Change: Not practical to increase delay as a very long delay is needed for the link to go down. Added code to record the proper link speed and duplex when speed is forced so that ethtool will return the proper speed without the link going down. Note that the link will go down if the link partner has autoneg turned on, ensuring that the link partner will see the link change. Impact: None. Enhancements: ------------- 1. Change: Added power management and WOL during device close. This will allow WOL to work after Linux shutdown. Impact: None. 2. Change: Changed driver so that ethtool will report invalid speed after ifdown. Impact: None. 3. Change: Updated tpatfw.h Impact: None. v1.0.7 (Sep. 14, 2004) ====================== Fixes: ------ 1. Problem: (CQTO523) 5706 A1 hangs after a thousand iterations of load/ifup/ifdown/unload. Cause: The driver may be servicing an interrupt within 15 msec of chip reset, causing the chip to hang. The problem was aggravated by the timer mode coalescing which created an excessive number of interrupts (hardware problem). The Driver may also occasionally see the wrong firmware signature that will cause it to abort. Change: Added synchronization to make sure all pending interrupts are serviced before resetting the chip. Also changed to collect mode coalescing. The firmware signature problem will be fixed in boot code. Impact: The use of collect mode coalescing may affect performance. 2. Problem: (CQTO558) Unable to load driver on some early 2.6 kernels. Cause: pci_dma_sync_single_for_* routines not defined on early 2.6 kernels. Change: Added compatibility defines for earlier kernels. Impact: None. v1.0.6 (Sep. 08, 2004) ====================== Fixes: ------ 1. Problem: (CQTO523) 5706 A1 hangs during repeated driver ifup/down. Cause: No delay after chip reset for A1. Change: Added 15 msec delay after chip reset for A1. Impact: None. 2. Problem: (CQTO468) Link does not go down after changing from 10Mbps full (forced) to 10Mbps half (forced) and vice versa. Cause: Not enough delay after forcing link down. Change: Added proper delay for link to go down. Impact: None. v1.0.5 (Sep. 02, 2004) ====================== Enhancements: ------------- 1. Change: Added support for ethtool -c, ethtool -C, ethtool -p, and firmware version for ethtool -i. Impact: None. Fixes: ------ 1. Problem: 5706C not advertising 1000 half duplex. Cause: 1000 full duplex overwrites 1000 half duplex. Change: Fixed the bug so that the 2 bits are or'ed together. Impact: None. 2. Problem: ethtool -A does not change the flow control settings in all cases. Cause: Flow control settings not zeroed out before setting new values. Change: Minor bug fix to zero out the value. Impact: None. v1.0.4 (Sep. 02, 2004) ====================== Fixes: ------ 1. Problem: (CQTO504) Multiple NFS transfers will hang some connections. Cause: Driver discards some receive packets when the error status is non-zero. Change: Changed the driver to only discard receive packets when the defined error bits in the error status are non-zero. Impact: None. v1.0.3 (Sep. 01, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not support ethtool -t self test and ethtool -S statistics. Change: Added ethtool self test and statistics. Impact: None. Fixes: ------ 1. Problem: (CQTO478) Kernel still panics when transmitting certain files using NFS after many iterations Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall. Change: More fixes made in firmware. Impact: None. v1.0.2 (Aug. 26, 2004) ====================== Enhancements: ------------- 1. Problem: Driver does not work on big endian machines. Change: Ported and tested on SPARC64 machine. Impact: None. Fixes: ------ 1. Problem: (CQTO478) Kernel panics when transmitting certain files using NFS. Cause: Tx DMA stalls on certain UDP packets, causing NFS client to stall. Change: Fixed in firmware. Impact: None. 2. Problem: (CQTO469) Unable to modify flow control parameters Cause: Did not call setup_phy after the parameters are changed. Change: Added call to setup_phy after parameters are changed. Impact: None. 3. Problem: (CQTO467) 5706 does not autonegotiate properly after changing settings with ethtool. Cause: This is an ethtool limitation as the proper advertising parameters are not passed to the driver properly. Change: Implemented a new scheme to work around the problem to allow users to specify full autoneg, single speed autoneg, and fixed speed. Impact: None. 4. Problem: ethtool -e does not work. Cause: Various bugs in the nvram routines. Change: Fixed and tested nvram routines on little endian and big endian machines. Impact: None. v1.0.1 (Aug. 18, 2004) ====================== Fixes: ------ 1. Problem: (CQTO459) 5706 NIC does not get link. Cause: Boot code timing out in WAIT2 state before driver is ready. Change: Moved the WAIT2 state ahead in the driver reset sequence as a temporary workaround until it is fixed in boot code. Impact: None. 2. Problem: (CQTO463) Kernel panics when loading the driver on RH30EL (2.4.21-4.EL) Cause: Older kernel used different API to allocate and register netdev. Change: Added older APIs to be used on older kernels. Impact: None. v1.0.0 (Aug. 13, 2004) ====================== Initial release