diff options
| author | Larry Finger <Larry.Finger@lwfinger.net> | 2009-11-23 18:40:45 -0600 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2009-12-04 13:28:49 -0500 |
| commit | c2ff581acab16c6af56d9e8c1a579bf041ec00b1 (patch) | |
| tree | 28f3e0a0cd1ba7582f5681a6a3902b78fe8bb9ec /drivers/net/wireless/b43legacy/rfkill.c | |
| parent | 9bf22f2c4607dbb68beb26153d83fa52b82e2d2f (diff) | |
| download | kernel_samsung_smdk4412-c2ff581acab16c6af56d9e8c1a579bf041ec00b1.zip kernel_samsung_smdk4412-c2ff581acab16c6af56d9e8c1a579bf041ec00b1.tar.gz kernel_samsung_smdk4412-c2ff581acab16c6af56d9e8c1a579bf041ec00b1.tar.bz2 | |
b43: avoid PPC fault during resume
The routine b43_is_hw_radio_enabled() has long been a problem.
For PPC architecture with PHY Revision < 3, a read of the register
B43_MMIO_HWENABLED_LO will cause a CPU fault unless b43_status()
returns a value of 2 (B43_STAT_STARTED) (BUG 14181). Fixing that
results in Bug 14538 in which the driver is unable to reassociate
after resuming from hibernation because b43_status() returns 0.
The correct fix would be to determine why the status is 0; however,
I have not yet found why that happens. The correct value is found for
my device, which has PHY revision >= 3.
Returning TRUE when the PHY revision < 3 and b43_status() returns 0 fixes
the regression for 2.6.32.
This patch fixes the problem in Red Hat Bugzilla #538523.
Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
Tested-by: Christian Casteyde <casteyde.christian@free.fr>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/b43legacy/rfkill.c')
0 files changed, 0 insertions, 0 deletions