Larry, can you attach an SPROM dump of your PCI BCM4318? I'm suffering from the exact same problem, and it would be interesting to find out what is actually happening. Also, what card do you have? (Mine is an Asus WL-138G V2 R3.01, but R3.00 is affected too.) Please attach an lspci -v and lspci -vn output too (or at least the revision number reported by lspci).
On Mon, Apr 14, 2008 at 2:36 AM, Larry Finger <[EMAIL PROTECTED]> wrote: > Stefano Brivio wrote: > > On Tue, 08 Apr 2008 14:11:04 -0500 > > Larry Finger <[EMAIL PROTECTED]> wrote: > > > >> 1. BCM4301 - With the ssb patch fixing IRQ TPS flag handling, I was > >> finally able to read beacons; however, no output interrupts were > >> delivered. > > > > [...] > > > >> I'm still looking for some differences > >> between bcm43xx and b43legacy regarding B-PHY and/or radio > >> initialization. > > > > Same here, without any appreciable result. Packets reach the PHY, and > the > > radio seems to be set up correctly, but still nothing hits the air. I'll > > investigate further. > > > > Out of curiosity, do you get weird values for LEDs in SPROM too? On my > > bcm4301, it looks like a lot of values in SPROM are unknown or somehow > > misinterpreted, like these ones: > > [ 6781.374512] b43legacy-phy2 warning: LEDs: Unknown behaviour 0x44 > > [ 6781.374520] b43legacy-phy2 warning: LEDs: Unknown behaviour 0x46 > > [ 6781.374527] b43legacy-phy2 warning: LEDs: Unknown behaviour 0x12 > > [ 6781.374534] b43legacy-phy2 warning: LEDs: Unknown behaviour 0x4D > > > > But I don't actually think that this is causing the issues we are seeing > > with TX. > > I don't either. Yes, I got those same warnings until I turned RFKILL, > etc. off in my config. In any case, the LEDS are in the back where I > cannot see them anyway. > > Do you have any PCI (not Cardbus) devices that work with b43? Do you > know of anyone that does? > > I tried my PCI-based BCM4318 with the version of b43 that was > introduced in the 2.6.24 merge, but it didn't work either. I can > receive data, but not transmit. The code gets all the way to where it > pokes the DMA transmission, and the interrupts are all enabled > correctly, but no TX interrupts are delivered. This is a regression > against bcm43xx, but has been in b43 and b43legacy since they were > introduced into mainline. My gut says that both b43 and b43legacy are > affected by a common problem. I no longer have a wireless-2.6 tree to > check back further, but it may be necessary to do so. > > Larry > _______________________________________________ > Bcm43xx-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
