📄 release.txt
字号:
Release Notes
Broadcom BCM5700 Linux Driver
Version 7.4.11
12/15/2004
Broadcom Corporation
16215 Alton Parkway,
Irvine, CA 92619-7013
Copyright (c) 2000-2004 Broadcom Corporation
All rights reserved
v7.4.11 (December 15, 2004)
=========================
1. Problem : (CQ11674)Driver diskette image for Red Hat 3.0 does
not work.
Cause : Red Hat 3.0 could not resolve an external function
during the image download. The compiler version
being used was not compatible witht he boot image.
Change : The driver disk image must be built on a
Red Hat system using gcc version 2.2.2.
gcc v2.2.2 seems to build the image that
Red Hat 3.0 accepts.
Impact : None.
Enhancement : The release format has been changed by splitting the
bcm5700-7.4.11.tar.gz into two files. The two files
are bcm5700-7.4.11.tar.gz which now contains the .TXT
files and src code, and the new bcm_sup-7.4.11.tar.gz file
which contains the Red Hat 3.0 kernel patch and driver
image files.
v7.4.10 (December 3, 2004)
=========================
1. Problem : (CQ11042)ASF IP Monitoring cannot update config table.
Cause : The NVRAM on 5750 LOM systems could not be written as
the NVRAM write protection was not being cleared by
the driver.
Change : The driver now correctly uses the write protection
capabilities of the 5750 LOM NVRAM.
Impact : The driver can write to the NVRAM for 5750 LOMs.
v7.4.9 (December 1, 2004)
=========================
1. Problem : EEPROM_ExecuteCommand warnings showing up on the console.
Cause : Code incorrectly uses old EEPROM routines.
Change : Use new nvram routines when available.
Impact : Flash works as expected.
2. Problem : (CQ11472)Add PLL workaround.
Cause : Occasionally a problem occurs when the device is put
into D3 cold. The problem can result in a chip lockup.
This only occurs on 5750 AX/BX chips.
Change : Added the workaroud to code, which is to keep the
power clks ticking when transitioning to d3 cold/hot.
Impact : D3 transition is robust.
v7.4.8 (November 24, 2004)
=========================
1. Problem : Vpd cannot be read on 5704 and other legacy devices.
Cause : Code incorrectly identifies flash type.
Change : Ignore bits 24 and 25 on Config1 for legacy devices.
Impact : Flash works as expected.
2. Problem : (CQ11402) Driver crashes while obtaining chip size on 5701.
Cause : Code uses incorrect read routine. Chipsize was not
initialized which caused a divide by zero.
Change : Change code to use correct read routine. Made sure
to set the chipsize to a valid chipsize (nonzero)
before calling the read routine.
Impact : EEPROM works as expected.
3. Problem : Firmware version not correct for 5721 devices.
Cause : Offset calculation error for Atmel parts.
Change : Fix calculation error.
Impact : Firmware version correct.
v7.4.7 (November 18, 2004)
=========================
1. Problem : Firmware version not displaying on BCM5753 devices.
Cause : Reads being performed before the NVRAM is locked.
Change : Lock the NVRAM before performing any reads.
Impact : None.
2. Problem : (CQ11142) OOPS occuring on PPC750
Cause : Statistic and status memory pointers were initialized
even after driver shutdown and memory deallocation
causing OOPS to occur when statistics were probed.
Change : Reset pointers to zero after shutdown.
Impact : None.
3. Problem : (CQ11115) Driver allows for invalid user adminstered
MAC address.
Cause : Driver did not check for valid address.
Change : Driver checks for valid MAC address.
Impact : None.
4. Problem : (CQ10598) Driver occasionally cannot get link on certain
machines.
Cause : The certain machines had interrupt sharing between many
devices and occasionally the driver would lose the
link change interrupt.
Change : The ISR was modified to ensure the interrupt being cleared
has been serviced properly.
Impact : None.
5. Problem : (CQ11117) Need SERDES pre-emphasis support.
Cause : Certain 5704 designs have requested that certain bits be
set in SERDES configuration registers.
Change : Changes made use presupplied value for SERDES configuration.
Impact : None.
Enhancement :
-------------
1. Change : GPIO2 will not have an output for the 5753 family.
2. Change : Added code to support more flash (and EEPROM) types.
The flash write code has been separated into buffered
and unbuffered versions. The flash and EEPROM read
code has been modified to support sub-32bit word reads.
New nvram sizing functions have been introduced.
v7.4.6 (October 25, 2004)
=========================
1. Problem : (CQ11088) Remove the ability to set speed & duplex on the 150T
Cause : The switch on the 150T nic is set to autoneg. The line speed
on the 5705 should only be set to auto for proper link to
be established with the internal switch.
Change : Added code in b57um.c line 4316 to check for this nic and
always set it to auto.
Impact : None.
2. Problem : (CQ11102) NMI occurs during load/unload w/ASF enabled.
Cause : The 5753 drove GPIO2 as an output, which did not allow
ASF to use it to sense main power properly.
Change : The driver does not driver GPIO2.
Impact : None.
v7.4.5 (October 11, 2004)
========================
Enhancement:
------------
Change: PCI IDs were added to support the 5753, 5753M, 5753F and 5789.
Impact: None.
v7.4.4 (October 4, 2004)
=======================
1. Problem : (CQ10955) DELL 6650 kernel panic during negotiation
using 5700 lom.
Cause : Spinlock deadlock during reset & link up.
Change : Removed the spinlock contention.
Impact : None.
2. Problem : (CQ10436)Man page needs update.
Cause : bcm5700.ko was not noted in man page.
Change : Modified man page.
Impact : None.
3. Problem : (CQ10396) Cannot ping when Dell PowerEdge 6650(#459)
is configured for 10half forced.
Cause : 5411 PHY does not require a PHY reset before being set
up to 10 half, or a PHY reset was being called without
sufficient delay before the PHY was being set up.
The code in LM_ResetAdapter()calls
LM_ResetPhy()(on line 3479 in tigon3.c) immediately before
calling LM_SetupPhy().
If a 2 second delay is placed between these two functions,
then 10half forced will function, or when LM_ResetPhy()
is removed, 10half forced will again function.
It is not clear why This delay is needed or why
LM_ResetPhy()is needed here as the MII control reg shows
the same values for a successful or failed case.
LM_ResetPhy() is not called for the 5401 PHY for the
same reason this problem occurs.
A request for assistance was emailed to HWEng with no
response.
Change : Removed unnecessary PHY reset for 5411 PHY.
Impact : Forcing 5411 PHY to 10 half will function as expected.
v7.4.3 (August 26, 2004)
======================
Fixes:
------
1. Problem : (CQ10437) Driver is installed in a directory other
than the directory noted in the README.TXT file.
Cause : Note omission.
Change : Added a line in the README.TXT file diclosing an
alternative install directory
(/lib/modules/<kernel_version>/kernel/drivers/net/bcm/)
for SLES9 installations.
Impact : Problem resolved.
2. Problem : (CQ10396) Cannot ping when Dell PowerEdge 6650(#459)
is configured for 10half forced.
Cause : 5411 PHY does not require a PHY reset before being
forced to 10 half.
Change : Removed unnecessary PHY reset for 5411 PHY.
Impact : Forcing 5411 PHY to 10 half will function as expected.
3. Problem : (CQ10540)Max value for "stats_coalesce_ticks" is
rejected in 2.6 kernels.
Cause : 2.6 kernels are using a different parameter interface
that limits the value range.
Change : README.TXT was changed to inform the user that the
value range for this parameter may very by kernel version.
Impact : None.
4. Problem : (CQ9804)5751 freezes in certain platforms under heavy
stress.
Cause : A logic bug in clearing interrupts caused this to occur.
See previous entry for CQ9804.
Change : Setting Bit 29 in 0x7c00 (TLP control reg) prevents
the lock-up from occurring and was set as a safeguard.
Impact : None.
Enhancement: (CQ10355) Ethtool -i shows no value for "firmware-version"
------------
Change : Added bootcode version value to Ethtool driver info structure.
Impact : None.
v7.4.2 (July 29, 2004)
======================
Fixes:
------
1. Problem:(CQ10695) System screen froze after third port.
Cause: Third port was pci and driver was treating it
as a pciexpress. Bug introduced v7.4.1.
Change:Driver checks for PCIE or PCI and then executes
PCIE code only on PCIE adapter.
Impact:Problem resolved.
2. Problem:(CQ10627)Remove 5751-A0 support.
Cause: 5751-A0 is not shipping.
Change:Driver checks for 5751 A0 then fails if found.
Impact:Driver will not load on 5751-A0
v7.4.1 (July 27, 2004)
======================
Fixes:
------
1. Problem:(CQ10602) FSC 1899 system may freeze/reboot when bringing the
initerface up/down with ASF enabled.
Cause: Handshake between ASF & driver disrupted by 7.4.0 extra
delay, allowing the driver to enable D3 state before ASF
was ready.
Change: Delay was moved to immediately before enabling D3.
Impact: Driver will not freeze or reboot system.
2. Problem:(CQ10481)Driver displays gigabit speed on adapter
that only supports 10/100.
Cause: The Driver displayed support for 10/100/1000 link
do to an error in the code.
Change: Code changed to display correct link support
values.
Impact: Driver displays correct supported link speeds.
v7.4.0 (July 12, 2004)
======================
Enhancement:
------------
Change: Added extra delay after GRC reset to make the
firmware D3hot workaround in 3.29i effective.
Impact: None.
Fixes:
------
1. Problem: (CQ10549) "BCM_DRV: command not found" when compiling
the source RPM.
Cause: $(BCM_DRV) not substituted properly.
Change: Changed all $(BCM_DRV) to $BCM_DRV in bcm5700.spec.
Impact: None.
2. Problem: (CQ10468) Driver not working properly in bridging environment
after changing mtu.
Cause: Promiscuous mode not preserved after changing mtu.
Change: Fixed by setting the rx mode after mtu change.
Impact: None.
3. Problem: (CQ10557) Kernel panics with 17 or more devices installed.
Cause: Driver parameters checking logic assumes maximum of 16
devices.
Change: Added logic to skip parameter processing if the device
index is higher than or equal to 16.
Impact: This will prevent the kernel panic and the driver will load with
any number of devices in the system. Driver parameters will
only work for the first 16 devices.
4. Problem: Changing mtu may cause the kernel to print a warning message:
sleeping function called from invalid context at mm/slab.c.
Cause: Calling kmalloc with GFP_KERNEL from invalid context.
Change: Changed to GFP_ATOMIC.
Impact: None.
v7.3.5 (June 23, 2004)
======================
Fixes:
------
1. Problem: (CQ10407) Linux 2.6 kernel fails to get IP address using DHCP
on 5751 A1.
Cause: When DHCP fails, ifup script will shutdown the NIC and it
will go to D3hot state. On 2.6 kernels, the config write
to put device in D3hot will be written using mmconfig with
a mmconfig read of register 0 to flush the write. The
read immediately following the write when the device is
transitioning to L1 link state may cause problems. The symptom
is that the device will lose the memory space bit in the
PCI command register. When ifup brings up the NIC again
to retry DHCP, the device will not be functional.
Change: The fix for the problem is in bootcode 3.29 which will
greatly reduce if not eliminate this problem from happening.
To further reduce the risk, 2 changes were made to the driver.
1. Add a parameter to disable D3hot (disable_d3hot).
2. Check PCI command register and re-enable the memory space
and other bits multiple times until the bits are set
or up to a maximum during driver init.
Impact: None.
v7.3.4 (June 18, 2004)
======================
Fixes:
------
1. Problem: (CQ10312) System Hangs when loading and unloading the driver
continuously with 5705.
Cause: Hang was caused by infinite retry soon after writing to register
0x74 to speed up the core clock.
Change: Implemented a 2-step sequence to speed up the core clock on
5705 and shasta devices.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -