kala mazoo wrote: > Greets, > > ---------------------------------------- >> Date: Tue, 6 May 2008 22:33:52 -0500 >> From: [EMAIL PROTECTED] >> To: [EMAIL PROTECTED] >> CC: [email protected] >> Subject: Re: ASUS WL-138G v2 / 64bit x86 / b43 working much better >> >> > <> >>> SPROM(0x64, LED 0 behaviour) = 0xFF >>> SPROM(0x65, LED 1 behaviour) = 0xFF >>> SPROM(0x66, LED 2 behaviour) = 0xFF >>> SPROM(0x67, LED 3 behaviour) = 0xFF >>> >>> ....then they're actually the -same- in both sprom image varients. >>> >>> Apparently there's more than just these bits in the sprom controlling the >>> LED >>> behaviour? Does anyone know what that might be? >> I'm not sure what you should expect from the 0xFF values; however, you have >> not enabled the LED select stuff in your kernel. If you had, you would see >> lines like >> >> b43-phy0 debug: 64-bit DMA initialized > > ....if it's supposed to say '64bit' , it doesn't here...
That is a function of your card, not your OS. Mine is 64-bit, yours is 32-bit, and others are 30-bit. >> Registered led device: b43-phy0::tx >> Registered led device: b43-phy0::rx >> Registered led device: b43-phy0::radio >> >> Larry > > ...weird. I went back to check the config, and the LED stuff was > actually enabled, albeit with led-class as a module. Then I noticed > 'LED trigger' support wasn't enabled in networking-->wireless. I > now know how this happens (aside from stupid human error). > > Using kernel menuconfig, one will typically configure networking-->wireless > before they get to device drivers-->LED support. This is unfortunate if one > has started the kernel configuration with devices drivers-->led support-->led > trigger support > unset, as led trigger support isn't displayed in networking-->wireless with > this option unset. Yes, configuration is not a straight-line process. In LKML, they are currently discussing changes that would gray out those options that do not have their prerequisites met. > Still stupid human error, I know, but that's how a person gets led into it. > > Anyhow, thanks for pointing that out, now I get ; > > b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) > b43-phy0 debug: Chip initialized > b43-phy0 debug: 32-bit DMA initialized > Registered led device: b43-phy0::tx > Registered led device: b43-phy0::rx > Registered led device: b43-phy0::assoc > b43-phy0 debug: Wireless interface started > b43-phy0 debug: Adding Interface type 2 > ....... > > The rx/tx LED behaviour is working as expected with the 0xFF sprom values > that come with this asus card type....afaict. Glad to be able to fix a problem quickly. Lately, it has been taking a long time. Perhaps the bugs are getting more subtle. Once again, thanks for the ASUS PCI card. I didn't do very much toward fixing the problem, but I was able to confirm that there was really a problem, and your difficulties weren't due to your spelling of behavior, the sun being in the north, or any other geographic factors. I'm particularly sensitive to the differences between British and American spelling. I once co-authored a book with another American. It was published by Wiley and Sons out of their UK office. The text went in with US spelling, but the galley proofs had UK spelling. We dutifully changed them all, but that had no effect. In the final version of the book, color was spelled colour, etc. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
