linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] rt2800: Initialize max_txpower to MAX_G_TXPOWER and MAX_A_TXPOWER respectively
Date: Tue, 22 May 2012 10:38:27 +0200	[thread overview]
Message-ID: <4FBB5083.4000606@01019freenet.de> (raw)
In-Reply-To: <4FB769DF.5060400@01019freenet.de>

Andreas Hartmann wrote:
> Helmut Schaa wrote:
>> On Fri, May 18, 2012 at 6:21 PM, Tobias Diedrich <ranma@tdiedrich.de> wrote:
>>>> So, maybe we should do it the safe way and just register a safe default
>>>> of 20dBm for all channels?
>>>
>>> AFAIU that would cap you to 20dBm even if you are in a country that
>>> has higher limits (e.g. 27dBm in the US?).
>>
>> Not necessarily because the driver won't allow tx power adjustments at all
>> if EEPROM_EIRP_MAX_TX_POWER is unused.
> 
> This means:
> Tx settings in cfg80211 as given by "iw reg get" e.g. are ignored
> completely as long as EEPROM_EIRP_MAX_TX_POWER is unused.
> Thus it is more or less chance that the device actually uses the allowed
> / correct Tx power at all. Maybe it's too high or too low. Both would be
> bad.

Please Helmut, I would be really grateful if you could confirm or negate
my conclusion.

>> For these devices we cannot rely on the tx power output at all and maybe
>> it makes sense to register a max power of 0 just to tell mac80211/cfg80211
>> that no tx power adjustments are possible on these devices?
> 
> Hmmm, this sounds really strange. How can I see if a device uses
> EEPROM_EIRP_MAX_TX_POWER at all?
> It would be good to have a log entry, telling the user that the Tx power
> of the device can't be adjusted at all and therefore it is possible,
> that the operation of the device might be illegal in the current country
> even if cfg80211 is set correctly.


Thank you Helmut,
kind regards,
Andreas

  reply	other threads:[~2012-05-22  8:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 23:04 [PATCH] rt2800: Initialize max_txpower to MAX_G_TXPOWER and MAX_A_TXPOWER respectively Tobias Diedrich
2012-05-18  6:57 ` Gertjan van Wingerde
2012-05-18  9:18 ` Helmut Schaa
2012-05-18 12:13   ` Andreas Hartmann
2012-05-18 16:21   ` Tobias Diedrich
2012-05-19  8:14     ` Helmut Schaa
2012-05-19  9:37       ` Andreas Hartmann
2012-05-22  8:38         ` Andreas Hartmann [this message]
2012-05-22 10:02           ` Helmut Schaa
2012-05-22 11:26             ` Andreas Hartmann
2012-05-22 11:32               ` Helmut Schaa
2012-05-22 12:47                 ` Andreas Hartmann
2012-05-24  7:35                   ` Andreas Hartmann
2012-06-04 11:08             ` Stanislaw Gruszka
2012-06-04 12:24               ` Helmut Schaa
2012-05-22 11:33 ` Helmut Schaa
2012-05-22 20:58   ` Tobias Diedrich
2012-05-23 11:32     ` Helmut Schaa
2012-05-23 13:55       ` Tobias Diedrich
2012-05-23 19:30         ` Helmut Schaa
2012-05-23 20:51           ` Tobias Diedrich

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=4FBB5083.4000606@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --cc=helmut.schaa@googlemail.com \
    --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).