From: Johannes Berg <johannes@sipsolutions.net>
To: Vasanthakumar Thiagarajan <vasanth@atheros.com>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Handle power constraint level advertised in 11d+h beacon
Date: Mon, 05 Jan 2009 14:42:25 +0100 [thread overview]
Message-ID: <1231162945.3334.22.camel@johannes> (raw)
In-Reply-To: <20090105133738.GA21471@vasanth-laptop>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
On Mon, 2009-01-05 at 19:07 +0530, Vasanthakumar Thiagarajan wrote:
[an email that somehow was just an attachment?]
> > Also, I don't understand the subtraction? And why are you checking only
> > for sw scanning and not hw scanning?
>
> I think driver should handle in case of hw_scanning.
Yes, true, it's all per-channel too.
> > > +
> > > + if ((*pwr_constr_elem <= conf->channel->max_power) &&
> > > + (*pwr_constr_elem != conf->power_constr_level)) {
> > > + conf->power_constr_level = *pwr_constr_elem;
> > > + ieee80211_hw_config(sdata->local, 0);
> >
> > That needs a changed flag, no?
>
> No, ieee80211_hw_config() will take care.
Indeed, my mistake.
> > And how does the subtraction make sense
> > like this? The spec talks about the country element's max power, and
> > then subtracting this, to get the local power, but if the local power
> > was set lower than that then we shouldn't subtract even more, no?
>
>
> This is more concervative way of processing power constraint. Yeah, you are correct
> that we might be setting lower tx power than the allowed one when we subtract power
> constraint from already min power (of reg data base and 11d ie) instead of only power
> limit advertised in 11d ie, but this situation is uncommon.
Ok, makes sense, let's not worry about it then.
That means the unmodified patch is fine, I guess.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-01-05 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 9:36 [PATCH] mac80211: Handle power constraint level advertised in 11d+h beacon Vasanthakumar Thiagarajan
2009-01-05 11:12 ` Johannes Berg
2009-01-05 13:37 ` Vasanthakumar Thiagarajan
2009-01-05 13:42 ` Johannes Berg [this message]
2009-01-05 13:45 ` Vasanthakumar Thiagarajan
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=1231162945.3334.22.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=Vasanth.Thiagarajan@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vasanth@atheros.com \
/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