On 02/26/2010 09:27 AM, Gábor Stefanik wrote: > On Fri, Feb 26, 2010 at 4:13 PM, <[email protected]> wrote: >> On Feb 26, 2010 9:08am, Gábor Stefanik <[email protected]> wrote: >>> That's odd... the error only occurs when you stop the mmiotrace?! >> Yes, the error only occurs when I stop the mmiotrace with b43 loaded, or if >> I load b43 outside of an mmiotrace. >> >>> BTW no need to load wl and b43 on the same kernel - the effect of >>> loading wl survives a reboot or a kexec. >> But then I cannot get you the mmiotrace as you requested. If all you're >> after is the mmiotrace of b43 from cold and b43 from warm with wl magic, I >> can do that now. I don't know how helpful this will be given that b43 >> appears to work so long as an mmiotrace is being performed. > > The differences will still be there in the dump, even if something > related to mmiotrace seemingly works around the bug. > However, the most helpful logs would be the ones produced by wl > itself, on a cold boot.
This thread is most interesting. Thanks for keeping it on the list, even though the OP doesn't seem to know about "Reply All". The fact that the 4315 doesn't get the DMA errors until MMIO tracing is turned off suggests some kind of subtle timing difference. I'll look at the Broadcom code to see if there are some delay statements in the interrupt handling, or if their processing does things in a different order. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
