2012/7/26 Thomas Huehn :
> Hi Nick,
>
> Nick Kossifidis schrieb:
>
>> I think this is a better approach (I'll prepare a proper patch as soon
>> as I have some bandwidth to work with wireless-testing, maybe
>> tomorrow)...
>>
>> --- old/phy.c 2012-07-26 20:40:00.869150187 +0300
>> +++ new/phy.c 2012
Hi Nick,
Nick Kossifidis schrieb:
> I think this is a better approach (I'll prepare a proper patch as soon
> as I have some bandwidth to work with wireless-testing, maybe
> tomorrow)...
>
> --- old/phy.c 2012-07-26 20:40:00.869150187 +0300
> +++ new/phy.c 2012-07-26 20:43:25.074710577 +0300
> @@
2012/7/26 Felix Fietkau :
> On 2012-07-26 12:31 PM, Nick Kossifidis wrote:
>> 2012/7/26 Felix Fietkau :
>>> On 2012-07-26 12:20 PM, Nick Kossifidis wrote:
2012/7/26 Thomas Huehn :
> Hi Nick,
>
> Nick Kossifidis schrieb:
>
>> 2012/7/26 Thomas Huehn :
>
>> There is no
On 2012-07-26 12:31 PM, Nick Kossifidis wrote:
> 2012/7/26 Felix Fietkau :
>> On 2012-07-26 12:20 PM, Nick Kossifidis wrote:
>>> 2012/7/26 Thomas Huehn :
Hi Nick,
Nick Kossifidis schrieb:
> 2012/7/26 Thomas Huehn :
> There is nothing in your patch that suggests that
2012/7/26 Felix Fietkau :
> On 2012-07-26 12:20 PM, Nick Kossifidis wrote:
>> 2012/7/26 Thomas Huehn :
>>> Hi Nick,
>>>
>>> Nick Kossifidis schrieb:
>>>
2012/7/26 Thomas Huehn :
>>>
There is nothing in your patch that suggests that's related to this.
Anyway there's a simple way to fi
On 2012-07-26 12:20 PM, Nick Kossifidis wrote:
> 2012/7/26 Thomas Huehn :
>> Hi Nick,
>>
>> Nick Kossifidis schrieb:
>>
>>> 2012/7/26 Thomas Huehn :
>>
>>> There is nothing in your patch that suggests that's related to this.
>>> Anyway there's a simple way to fix this:
>>>
>>> Just move this:
>>>
>
2012/7/26 Thomas Huehn :
> Hi Nick,
>
> Nick Kossifidis schrieb:
>
>> 2012/7/26 Thomas Huehn :
>
>> There is nothing in your patch that suggests that's related to this.
>> Anyway there's a simple way to fix this:
>>
>> Just move this:
>>
>> 3575 /* Min/max in 0.25dB units */
>> 3576
Hi Nick,
Nick Kossifidis schrieb:
> 2012/7/26 Thomas Huehn :
> There is nothing in your patch that suggests that's related to this.
> Anyway there's a simple way to fix this:
>
> Just move this:
>
> 3575 /* Min/max in 0.25dB units */
> 3576 ah->ah_txpower.txp_min_pwr = 2 * rate
2012/7/26 Thomas Huehn :
> Hi Nick,
>
> Nick Kossifidis schrieb:
>
>> 2012/7/23 Thomas Huehn :
>>> In such cases where phy_init() function got called, tx_power is always
>>> set to ah->ah_txpower.txp_cur_pwr which is never updated with txpower
>>> specified by the user instead it equale max chan po
Hi Nick,
Nick Kossifidis schrieb:
> 2012/7/23 Thomas Huehn :
>> In such cases where phy_init() function got called, tx_power is always
>> set to ah->ah_txpower.txp_cur_pwr which is never updated with txpower
>> specified by the user instead it equale max chan power and got
>> potentially incremen
2012/7/23 Thomas Huehn :
> In such cases where phy_init() function got called, tx_power is always
> set to ah->ah_txpower.txp_cur_pwr which is never updated with txpower
> specified by the user instead it equale max chan power and got
> potentially incremented by ah_txpower.txp_offset.
Never updat
On Mon, Jul 23, 2012 at 08:25:26PM +0200, Thomas Huehn wrote:
> > Did this / 2 move elsewhere or was it wrong before? Is txp_cur_pwr still
> > used for anything?
>
> the "/2" is not needed anymore as I also skipped the "*2" in
> ath5k_hw_set_txpower_limit .. so I avoid this calculations.
>
> Fel
Hi all,
After applying this 2 patches I got the following eeprom read on an
Wistron CM9:
[ 38.88] ath5k: phy0: [bluse ath5k_eeprom] rate_pcal_info[0].freq
= 4920, rate[0].target_power_6to24 = 36, rate[0].target_power_36 = 32,
rate[0].target_power_48 = 28, rate[0].target_power_54 = 24
[ 38
Hi Bob,
Bob Copeland schrieb:
> On Mon, Jul 23, 2012 at 06:01:15PM +0200, Thomas Huehn wrote:
>> /* Setup rate power table */
>> -ath5k_setup_rate_powertable(ah, txpower, &rate_info, ee_mode);
>> +ath5k_setup_rate_powertable(ah, ah->ah_txpower.txp_user_pwr,
>> &rate_info, ee_mode);
On Mon, Jul 23, 2012 at 06:01:15PM +0200, Thomas Huehn wrote:
> /* Setup rate power table */
> - ath5k_setup_rate_powertable(ah, txpower, &rate_info, ee_mode);
> + ath5k_setup_rate_powertable(ah, ah->ah_txpower.txp_user_pwr,
> &rate_info, ee_mode);
txpower used to be .5 dB units --
In such cases where phy_init() function got called, tx_power is always
set to ah->ah_txpower.txp_cur_pwr which is never updated with txpower
specified by the user instead it equale max chan power and got
potentially incremented by ah_txpower.txp_offset.
In any case the card was switching to a txpow
16 matches
Mail list logo
