Re: [PATCH 0/4] multi-channel/interface TX power handling

[Ben Greear <greearb@candelatech.com>]

On 10/24/2012 10:30 AM, Johannes Berg wrote:
> On Wed, 2012-10-24 at 09:31 -0700, Ben Greear wrote:
>
>>> Yeah that'd be the only way, most scripts I've seen always just use the
>>> interface anyway though? I'm not totally happy about this, maybe we
>>> should iterate all interfaces? Not really sure ...
>>
>> Well, I think we should make setting the wiphy work...just iterate
>> all interfaces.  Breaking backwards compatibility just causes too
>> much problems for user-space, and many users may either not notice,
>> or not be able to change whatever software is screwing up.
>
> Yeah I guess.
>
>> But, I think we also need some way to know if we can set individual
>> vifs to different tx-power successfully.
>>
>> Maybe a /sys/class/netdev/wlan0/tx-power file to read current power could
>> be added in this patch series?  Then user-space could key off of it's
>> existence, and it would give a simple way to read the current tx-power
>> settings (and possibly set it as well)...
>
> sysfs file sounds like about the worst possible way (except maybe for
> procfs), an nl80211 feature flag could be worthwhile though :)

Ok, a feature flag sounds fine to me.

Thanks,
Ben

>
> johannes
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com