Joseph Jezak wrote:
> 
> Sorry, the msleep, even at 1000, doesn't make a difference.  It seems to
> be taking about 65 cycles through the loop for the IRQ_READY flag to
> show up, with or without the msleep after suspend.    If I unload and
> reload the module during normal usage, it's only about 15 cycles.  Maybe
> Johannes has a better idea as to why, he's much more familiar with the
> firmware than I am.


Thanks for testing. For the others reading this message, the following patch 
seems to fix the oops
that follows a resume operation.

Larry

=========


Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx.h
===================================================================
--- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx.h
+++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx.h
@@ -21,7 +21,7 @@
 #define PFX                            KBUILD_MODNAME ": "

 #define BCM43xx_SWITCH_CORE_MAX_RETRIES        50
-#define BCM43xx_IRQWAIT_MAX_RETRIES    50
+#define BCM43xx_IRQWAIT_MAX_RETRIES    100

 #define BCM43xx_IO_SIZE                        8192



==============
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to