On Wed, Nov 23, 2011 at 2:07 AM, Rajkumar Manoharan <rmanohar@xxxxxxxxxxxxxxxx> wrote: > On Tue, Nov 22, 2011 at 10:10:00AM -0800, Luis R. Rodriguez wrote: >> By definition WIPHY_FLAG_STRICT_REGULATORY was intended to allow the >> wiphy to adjust itself to the country IE power information if the >> card had no regulatory data but we had no way to tell cfg80211 that if >> the card also had its own custom regulatory domain (these are typically >> custom world regulatory domains) that we want to follow the country IE's >> noted values for power for each channel. We add support for this and >> document it. >> >> This is not a critical fix but a performance optimization for cards >> with custom regulatory domains that associate to an AP with sends >> out country IEs with a higher EIRP than the one on the custom >> regulatory domain. In practice the only driver affected right now >> are the Atheros drivers as they are the only drivers using both >> WIPHY_FLAG_STRICT_REGULATORY and WIPHY_FLAG_CUSTOM_REGULATORY -- >> used on cards that have an Atheros world regulatory domain. Cards >> that have been programmed to follow a country specifically will not >> follow the country IE power. So although not a stable fix distributions >> should consider cherry picking this. >> > Luis, > > After some testing, I noticed that the incresed power value seems to be > remained after the disconnection. So while falling back to world > regulatory domain the band updations are ignored at ignore_reg_update. > If the driver follows STRICT_REGULATORY, the it should not be ignored. > isn't it? I'll look into this, thanks for testing. John please hold off on these patches, I will respin them along with my stable fixes. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
