On Fri, 2007-09-14 at 10:07 -0500, Larry Finger wrote: > David Woodhouse wrote: > > On Thu, 2007-09-13 at 14:44 -0500, Larry Finger wrote: > >> David, > >> > >> Please try the patch below. > > > > Differently buggered... now we hit the B43legacy_BUG_ON() in > > b43legacy_rx() -- at least that's the _last_ trace I captured from the > > screen; there were more further up. > > > > This device is basically identical to the one I handed to John in > > Cambridge last week. How do I force the b43 driver to bind to it? > > > > As you saw from Michael's message, basically you cannot. The latest drivers > and V4 firmware from > Broadcom have abandoned this device and the BCM4301, which is why b43legacy > is needed. It may work > at the moment, but it could fail with any revisions in the specs based on a > new Broadcom driver or > with new firmware.
OK, I'll concentrate on b43legacy then. > Too bad that the device behaves so differently with ppc architecture. None of > these problems happen > on my i386 platform. Performance is bad for OFDM rates, but otherwise the > interface is OK. The machine checks only don't show up because your PCI host bridge is more tolerant -- I bet you _could_ actually configure it to produce an NMI, if you really want that kind of behaviour when you poke at non-existent registers. I think that should be _encouraged_, in fact :) Or I can dust off the patch I used a while back to debug and recover from the machine checks. Unless it's endian-related I suspect the BUG() would probably occur on i386 too, with the CardBus card I gave away last week and the same revision of the kernel. Perhaps John can confirm that? (I'm using 2.6.23-0.181.rc6.git4.fc8 today) I'll poke at it some more when I get home this weekend. -- dwmw2 _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
