I think I am working on the first sanity check in the driver, but still cannot see any FCS error frames. Is setting B43_MACCTL_KEEP_BAD the only thing we need to do for the firmware?
Thanks, -Bo On Tue, Feb 17, 2009 at 5:54 PM, Michael Buesch <[email protected]> wrote: > Please read the code. There are lots of sanity checks in b43 and mac80211 > that make it impossible to receive completely corrupted frames. > > On Tuesday 17 February 2009 23:05:51 Bo Han wrote: > > Hi, > > > > I am interested in capturing FCS error frames using b43 driver. My > hardware > > information is as follows. > > > > b43-phy9: Broadcom 4318 WLAN found > > b43-phy9 debug: Found PHY: Analog 3, Type 2, Revision 7 > > b43-phy9 debuf: Found Radio: Manuf 0x17f, Version 0x2050, Revision 8 > > > > I am using firmware version 410.2160 with linux kernel version 2.6.27.10. > I > > told the firmware to keep the bad frames by setting ctl |= > > B43_MACCTL_KEEP_BAD just before b43_write32(dev, b43_MMIO_MACCTL, ctl) in > > b43_adjust_mode(...) in main.c. > > From b43_rx(...) in xmit.c, I can only see packets dropped because their > > rate_idx == -1. The length of all the dropped packets is 80 bytes and > they > > look like the following: > > > > 8fae 0308 0000 0b01 0085 0000 1500 482c > > 50b3 0b01 0085 0000 5fa0 1500 482c 50b3 > > aaaa 0003 850b cdcc 1b00 1d00 b945 c0cd > > b905 630a 5e10 0101 0601 0b06 000b 07d6 > > bab9 addb 35fd 33e8 cd8f 8eaa 6f77 b9e8 > > > > However, there is still no packet received with macstat > B43_RX_MAC_FCSERR. > > I also tried the 351 firmware for which I saw several FCS error frames in > > PIO mode. But the sniffing tools like Wireshark cannot get any packets. > > including the correct ones, when using that firmware. > > > > Am I missing something? > > > > Thanks, > > -Bo > > > > > > -- > Greetings, Michael. >
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
