On Fri, 2007-09-14 at 10:07 -0500, Larry Finger wrote: > The only way that b43legacy_rx() could generate a BUG_ON is if the > bitrate codes in the received > message are messed up. The attached patch will partially silence those > messages and let us see more. > Perhaps we can find the real cause. I certainly appreciate your > assistance in debugging these problems.
With this patch and the later le16_to_cpu(rxhdr->mac_status) change, my device seems to be working with b43legacy: b43legacy-phy2: Broadcom 4306 WLAN found b43legacy-phy2 debug: Found PHY: Analog 1, Type 2, Revision 1 b43legacy-phy2 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 b43legacy-phy2 debug: Radio turned off wmaster0: Selected rate control algorithm 'simple' net eth1: device_rename: sysfs_create_symlink failed (-17) b43legacy-phy2 debug: Adding Interface type 2 b43legacy-phy2 debug: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27) b43legacy-phy2 debug: Radio turned on b43legacy-phy2 debug: Radio enabled by hardware b43legacy-phy2 debug: Chip initialized b43legacy-phy2 debug: 30-bit DMA initialized b43legacy-phy2 debug: Wireless interface started ADDRCONF(NETDEV_UP): eth1: link is not ready b43legacy-phy2 debug: Using software based encryption for mac: ff:ff:ff:ff:ff:ff eth1: Initial auth_alg=0 eth1: authenticate with AP 00:06:25:4b:55:f8 eth1: RX authentication from 00:06:25:4b:55:f8 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:06:25:4b:55:f8 eth1: RX AssocResp from 00:06:25:4b:55:f8 (capab=0x411 status=0 aid=1) eth1: associated eth1: switched to short barker preamble (BSSID=00:06:25:4b:55:f8) ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready -- dwmw2 _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
