summaryrefslogtreecommitdiff
path: root/target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch
diff options
context:
space:
mode:
authornbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>2010-07-10 00:48:37 +0000
committernbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73>2010-07-10 00:48:37 +0000
commit59da09e12dedf616af8614d2fc13ca57dcecf01a (patch)
tree0fb8cc99f5a6cb8bfce0c542065c2ccd70d7e913 /target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch
parentea1ef33b00cba335cc1084675ba1b7f1b77e3dde (diff)
Get rid of the b44 'BUG! Timeout waiting for bit 80000000 of register 428 to clear.' spam.
more and more users are getting confused by this, and consider it a regression in brcm47xx, because brcm-2.4 was not showing this message. It's not particularly interesting for debugging, most of the time it only happens because of an unconnected port. git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22110 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch')
-rw-r--r--target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch17
1 files changed, 17 insertions, 0 deletions
diff --git a/target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch b/target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch
new file mode 100644
index 0000000000..dbd46aee64
--- /dev/null
+++ b/target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch
@@ -0,0 +1,17 @@
+--- a/drivers/net/b44.c
++++ b/drivers/net/b44.c
+@@ -189,11 +189,13 @@ static int b44_wait_bit(struct b44 *bp,
+ udelay(10);
+ }
+ if (i == timeout) {
+- printk(KERN_ERR PFX "%s: BUG! Timeout waiting for bit %08x of register "
++#if 0
++ printk(KERN_DEBUG PFX "%s: BUG! Timeout waiting for bit %08x of register "
+ "%lx to %s.\n",
+ bp->dev->name,
+ bit, reg,
+ (clear ? "clear" : "set"));
++#endif
+ return -ENODEV;
+ }
+ return 0;