Although I found the right phy.c file in the kernel I'm using, I can't ensure I'm making the right changes. For instance, it seems like your refs in b43legacy_phy_xmitpower() is different than in my b43legacy file: max_pwr = dev->dev->bus->sprom.maxpwr_bg; vs max_pwr = dev->dev->bus->sprom.r1.maxpwr_bg;
Also, I'm not sure what the "hunk" is in the appropriate main.c mentioned below. >apply to -stable, or the 2.6.25-rcX code, delete the hunk that changes >drivers/net/wireless/b43legacy/main.c, as it will not apply to those >trees. Is it possible to point me to the location of the rf testing kernel so I can just use that? The sad part is that I feel like I should be able to tell what's going on, but it's hard to interpret code with so little in-line comments. Not trying to take a dig at anyone, just wish I could contribute somehow. It didn't seem like even the offset locations in http://bcm-specs.sipsolutions.net/SHM and http://bcm-specs.sipsolutions.net/PHYRegister were the same as those referenced in the code. For instance, I noticed reading and writing in lines like: b43legacy_phy_write(dev, 0x04A5, (b43legacy_phy_read(dev, 0x04A5) & 0x00FF) | 0x5700); but cannot tell where 0x04A5 is. I was attempting at replacing those hex references with a readable def value, but cannot even do that. Regards, Kurt ---------------------------------------------------------------------- Message: 1 Date: Sat, 05 Apr 2008 12:41:40 -0500 From: Larry Finger <[EMAIL PROTECTED]> Subject: Re: [PATCH RFT V2] b43legacy: Fix TX power adjustments To: KURT PETERS <[EMAIL PROTECTED]> Cc: [email protected], [EMAIL PROTECTED], [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed KURT PETERS wrote: > > You mentioned I couldn't use Linus's repository, so Where can I get a > revised kernel with these changes already in place (I'm running 2.6.24.3 > from kernel.org)? > kurt I didn't say that you couldn't use Linus's repository - only that you need to remove one hunk from the patch for it to work with 2.6.25-rcX. You can remove that same hunk and apply it to 2.6.24.3. There are no revised kernels with this patch in place! The patch is currently being tested and will/can not be incorporated into any kernel until it passes those tests. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
