summaryrefslogtreecommitdiff
path: root/drivers/net/wireless/ipw2200.h
diff options
context:
space:
mode:
authorZhu Yi <yi.zhu@intel.com>2006-01-24 08:37:22 (GMT)
committerJohn W. Linville <linville@tuxdriver.com>2006-01-31 01:35:34 (GMT)
commit397ae121ee0116d3b4125d621f0ef528d1d52580 (patch)
treeb4de052ca78d6c8b4c05494a4a297aac9e88190e /drivers/net/wireless/ipw2200.h
parent4bfdb91dcff0dd4b70922de263ccffffb8fb1d16 (diff)
downloadlinux-fsl-qoriq-397ae121ee0116d3b4125d621f0ef528d1d52580.tar.xz
[PATCH] ipw2200: Scale firmware loading watchdog with the firmware size
I can't really help with why restarts happen, but the following patch greatly increases the likelihood that a firmware reload will succeed afterward on my thinkpad. It addresses two issues. First, sysfs module loading and hotplug are asynchronous, and as such file operations on the "loading" and "data" files are racy when you load 2 firmwares in quick succession. Second, the timeout for DMAing the firmware needs to scale with the size of the firmware being loaded. That is, the watchdog needs to be on throughput, not on time alone. I no longer get the firmware load errors, though this is at best a hacky workaround for a racy interface. (Obviously, this does nothing to address the fatal errors in firmware which cause reloads; it just causes the initial loading and the reloads to work more often.) Signed-off-by: Peter Jones <pjones@redhat.com> Signed-off-by: Ben M Cahill <ben.m.cahill@intel.com> Signed-off-by: Zhu Yi <yi.zhu@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/ipw2200.h')
0 files changed, 0 insertions, 0 deletions