Larry Finger wrote: > This E-mail is to summarize what I have learned to date. > > The pm_qos change does nothing useful. It may have helped a little, but the > side > effects are far worse than the benefits. > > Most systems work better with b43 when warm booted after Broadcom's wl driver > was loaded. The conclusion is that wl is making some change in the setup that > b43 is not. > > (3) Based on the above, I have done MMIO and PCI-E configuration tracing for > the > two drivers and found some real differences. After seeing these, I did more RE > work, and found some setup for the PCI-E core that was missed earlier. I am > still working on the changes. What I have completed is found at > > http://bcm-v4.sipsolutions.net/PCI-E#PCI-E_Setup > > I doubt that most of these new routines will affect the problem interfaces as > they apply only to PCI-E core revisions 7 and 8. My BCM4312 has rev 9. I do > not > know what versions are giving the trouble. With SSB_DEBUG enabled, it will be > in > a log line as follows: > > ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) > > If you are seeing the DMA error, please supply the above info. > > The "PCI-E Miscellaneous Configuration" routine that is not yet finished does > run on my system and is the source of the tracing differences. If the problem > cards has a revision newer than 9, I will probably need an MMIO trace for your > device. > > Larry >
Here is mine. r...@mini ~ # dmesg | grep ssb [ 138.450389] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) [ 138.450420] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) [ 138.450447] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) [ 138.450473] ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) [ 138.490310] ssb: Found rev 1 PMU (capabilities 0x02A62F01) [ 138.499585] ssb: SPROM revision 8 detected. [ 138.533626] ssb: Sonics Silicon Backplane found on PCI device 0000:01:00.0 Just a note, I am testing it right now and you were right, the card does work if warm booted after having used wl driver. Seems like some initialization stuff is done differently, as the led turn active (blue ) even before loading any driver for the card. - William _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
