On Sun, Oct 25, 2009 at 11:08 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > > > On Sun, 25 Oct 2009, Chris Vine wrote: >> >> On Sun, 25 Oct 2009 22:40:50 +0100 Gábor Stefanik <netrolller...@gmail.com> >> suggested: >> > Another thing to test: boot into Windows (or any other OS where the [..] >> >> You already know that this eliminates the DMA errors. I have reported >> twice that if I boot up with the 2.6.27 kernel and install the broadcom >> b43 driver to intialise the wireless device, and then do a warm reboot >> to 2.6.32-rc5, then b43 works correctly. > > Is there some way to dump all the device registers behind the SSB bridge? > If so, dumping them for the warm-boot and cold-boot cases, and seeing > where they are different might be an obvious clue, and point to something > that isn't initialized correctly. >
I don't know of such a method; however I have previously succeeded in using mmiotrace to find differences between wl and b43, so it might be of help in this case. However, this might be completely irrelevant, as I suspect that PhoenixBIOS is interfering with the DMA mappings of the card, which wl (and the Windows driver) works around somehow. (Is this "PR41573"? In that case, it's possible that the calibration patch - maybe in conjunction with a proper PHY reset - will fix it.) Larry: what BIOS are you testing on? > And Chris, just out of interest - does FORCE_PIO work for you too? > > Linus > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
