linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] multi-channel/interface TX power handling
Date: Wed, 24 Oct 2012 09:31:28 -0700	[thread overview]
Message-ID: <508817E0.5050504@candelatech.com> (raw)
In-Reply-To: <1351093332.10709.5.camel@jlt4.sipsolutions.net>

On 10/24/2012 08:42 AM, Johannes Berg wrote:
> On Wed, 2012-10-24 at 08:40 -0700, Ben Greear wrote:
>> On 10/24/2012 03:13 AM, Johannes Berg wrote:
>>> This was the remaining work I had to do in mac80211, but it
>>> got a little larger because cfg80211 wasn't doing per-vif
>>> TX power ...
>>>
>>> I disallowed setting TX power per hardware now, we could in
>>> theory do something like set all interfaces in that case, but
>>> it seemed like a lot of work for very little gain. If someone
>>> needs it, we can do it later :-)
>>
>> Is there any good way for user-space to know if kernel supports
>> old or new version?  Maybe just try to set per wiphy and if that fails,
>> try to set per vif?
>
> 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.

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)...

Thanks,
Ben

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


  reply	other threads:[~2012-10-24 16:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 10:13 [PATCH 0/4] multi-channel/interface TX power handling Johannes Berg
2012-10-24 10:13 ` [PATCH 1/4] nl80211: move "can set channel" check Johannes Berg
2012-10-24 10:13 ` [PATCH 2/4] cfg80211: make TX power setting per interface Johannes Berg
2012-10-24 16:27   ` Ben Greear
2012-10-24 17:31     ` Johannes Berg
2012-10-24 17:38       ` Ben Greear
2012-10-24 10:13 ` [PATCH 3/4] mac80211: handle TX power per virtual interface Johannes Berg
2012-10-24 10:13 ` [PATCH 4/4] mac80211_hwsim: print per interface TX power Johannes Berg
2012-10-24 15:40 ` [PATCH 0/4] multi-channel/interface TX power handling Ben Greear
2012-10-24 15:42   ` Johannes Berg
2012-10-24 16:31     ` Ben Greear [this message]
2012-10-24 17:30       ` Johannes Berg
2012-10-24 17:39         ` Ben Greear
2012-10-24 23:05     ` Is Multi-Vif (vaps) Different Channel Operation Supported? Kelly Hogan
2012-10-24 23:56       ` Ben Greear
2012-10-27  8:19         ` Adrian Chadd
2012-10-27 18:19           ` Arend van Spriel
2012-10-28 22:06             ` Adrian Chadd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=508817E0.5050504@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).