diff options
| author | Ariel Elior <ariele@broadcom.com> | 2012-05-06 07:05:57 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2012-05-06 13:10:38 -0400 |
| commit | 24f06716cd5dbfc3d737ec2a24ac58ef76f68dc7 (patch) | |
| tree | 4d5ab71ca2f173ef85eaebaab8a20a0840cddf11 /include/linux/export.h | |
| parent | 6e1344e8088bd2de059a0fee4e15ddf6909fd833 (diff) | |
| download | linux-24f06716cd5dbfc3d737ec2a24ac58ef76f68dc7.tar.gz linux-24f06716cd5dbfc3d737ec2a24ac58ef76f68dc7.tar.bz2 linux-24f06716cd5dbfc3d737ec2a24ac58ef76f68dc7.zip | |
bnx2x: bug fix when loading after SAN boot
This is a bug fix for an "interface fails to load" issue.
The issue occurs when bnx2x driver loads after UNDI driver was previously
loaded over the chip. In such a scenario the UNDI driver is loaded and operates
in the pre-boot kernel, within its own specific host memory address range.
When the pre-boot stage is complete, the real kernel is loaded, in a new and
distinct host memory address range. The transition from pre-boot stage to boot
is asynchronous from UNDI point of view.
A race condition occurs when UNDI driver triggers a DMAE transaction to valid
host addresses in the pre-boot stage, when control is diverted to the real
kernel. This results in access to illegal addresses by our HW as the addresses
which were valid in the preboot stage are no longer considered valid.
Specifically, the 'was_error' bit in the pci glue of our device is set. This
causes all following pci transactions from chip to host to timeout (in
accordance to the pci spec).
Signed-off-by: Ariel Elior <ariele@broadcom.com>
Signed-off-by: Eilon Greenstein <eilong@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux/export.h')
0 files changed, 0 insertions, 0 deletions