On Thursday 17 April 2008 21:49:53 Stefanik Gábor wrote: > On Thu, Apr 17, 2008 at 5:18 PM, Michael Buesch <[EMAIL PROTECTED]> wrote: > > > [ 966.619496] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor > > 0x4243) > > [ 966.619496] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor > > 0x4243) > > [ 966.619496] ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243) > > [ 966.619496] ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor > > 0x4243) > > [ 966.637500] ssb: SPROM revision 2 detected. > > [ 966.658366] ssb: Sonics Silicon Backplane found on PCI device > > 0000:02:05.0 > > [ 966.674476] b43-phy3: Broadcom 4318 WLAN found > > [ 966.714105] b43-phy3 debug: Found PHY: Analog 3, Type 2, Revision 7 > > [ 966.714105] b43-phy3 debug: Found Radio: Manuf 0x17F, Version 0x2050, > > Revision 8 > > [ 966.734069] phy3: Selected rate control algorithm 'pid' > > [ 966.736778] Broadcom 43xx driver loaded [ Features: PNR, Firmware-ID: > > FW13 ] > > [ 988.593922] input: b43-phy3 as /class/input/input8 > > [ 987.781568] b43-phy3: Loading firmware version 351.126 (2006-07-29 > > 05:54:02) > > [ 987.781568] b43-phy3 warning: You are using an old firmware image. > > Support for old firmware will be removed in July 2008. > > [ 987.781568] b43-phy3 warning: You must go to > > http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download > > the latest firmware (version 4). > > [ 987.895936] b43-phy3 debug: Chip initialized > > [ 987.896206] b43-phy3 debug: 32-bit DMA initialized > > [ 988.967223] b43-phy3 debug: Wireless interface started > > [ 988.967247] b43-phy3 debug: Adding Interface type 2 > > [ 988.981264] phy3: HW CONFIG: freq=2412 > > [ 991.039238] b43-phy3 debug: Removing Interface type 2 > > [ 991.061533] b43-phy3 debug: Wireless interface stopped > > [ 990.024893] b43-phy3 debug: DMA-32 rx_ring: Used slots 0/64, Failed > > frames 0/0 = 0.0%, Average tries 0.00 > > [ 990.026360] b43-phy3 debug: DMA-32 tx_ring_AC_BK: Used slots 0/128, > > Failed frames 0/0 = 0.0%, Average tries 0.00 > > [ 990.031396] b43-phy3 debug: DMA-32 tx_ring_AC_BE: Used slots 0/128, > > Failed frames 0/0 = 0.0%, Average tries 0.00 > > [ 990.038040] b43-phy3 debug: DMA-32 tx_ring_AC_VI: Used slots 0/128, > > Failed frames 0/0 = 0.0%, Average tries 0.00 > > [ 990.048005] b43-phy3 debug: DMA-32 tx_ring_AC_VO: Used slots 0/128, > > Failed frames 0/0 = 0.0%, Average tries 0.00 > > [ 990.056402] b43-phy3 debug: DMA-32 tx_ring_mcast: Used slots 0/128, > > Failed frames 0/0 = 0.0%, Average tries 0.00 > > > Hmm, that looks like no data reaches the TX rings.
Yeah, because I didn't transmit anything. > For comparision, can you > post the output of a non-Asus 4318? What happens if you flash a non-Asus > SPROM into the card? Yeah well. Most likely nothing. This data wasn't meant for giving me advise on how to proceed. It was more to show what card that really is and people can compare that to their card. However, the two fully working 4318 that I own have _exactly_ the same core and PHY revisions like this one. It seems that I can DMA data to the device, but the firmware cannot handle it properly. But I must confirm this first by doing some debugging on the microcode. When I try to transmit a packet with a corrupt TX header nothing happens. It should actually produce a PHY error in that case. So I _think_ that the problem is some packet handling in the firmware. Now sure yet, however, as I have to verify my theories first. Printing the status reports of the DMA engine seems to indicate that it works properly. There's also no power emmitted by the device (except for half a second during PHY initialization.) -- Greetings Michael. _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
