From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] hostAPd operating in 5Ghz channels
Date: Fri, 3 Apr 2009 15:01:22 -0700 [thread overview]
Message-ID: <20090403220122.GF10278@tesla> (raw)
In-Reply-To: <8336C6E0-EC2F-43EE-9B61-3780149C880C@gmail.com>
On Fri, Apr 03, 2009 at 02:44:00PM -0700, Giorgio Mazzucchelli wrote:
>
> > Please don't retell error messages and don't assume that you are doing
> > something wrong.
>
> OK, sorry for that.
>
> > Please give exact commands you are using, and explain
> > how you see that they are not working.
>
> iw reg set IT
>
> Frequencies:
> * 5180 MHz [36] (17.0 dBm)
> * 5200 MHz [40] (17.0 dBm)
> * 5220 MHz [44] (17.0 dBm)
> * 5240 MHz [48] (17.0 dBm)
> * 5260 MHz [52] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5280 MHz [56] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5300 MHz [60] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5320 MHz [64] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5500 MHz [100] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5520 MHz [104] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5540 MHz [108] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5560 MHz [112] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5580 MHz [116] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5600 MHz [120] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5620 MHz [124] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5640 MHz [128] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5660 MHz [132] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5680 MHz [136] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5700 MHz [140] (20.0 dBm) (passive scanning, no IBSS,
> radar detection)
> * 5745 MHz [149] (disabled)
> * 5765 MHz [153] (disabled)
> * 5785 MHz [157] (disabled)
> * 5805 MHz [161] (disabled)
> * 5825 MHz [165] (disabled)
>
> iw reg set US (or FR, DE... whatever)
> prints the same frequencies listed above.
>
> modbrobe cfg80211 ieee_regdom=IT (or US, FR, DE...)
> doesn't change anything.
This is by design -- if the card has a regulatory domain set
programmed into it, you won't be able to override it. So its not
that its failing its more that the card already has its regulatory
information properly programmed. This goes for Intel and Atheros wireless
cards. Cards that have no regulatory implementations though can benefit
from user input as there is none -- that accounts for the rest of the cards.
Luis
prev parent reply other threads:[~2009-04-03 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 8:20 [ath9k-devel] hostAPd operating in 5Ghz channels Giorgio Mazzucchelli
2009-04-03 8:33 ` Jouni Malinen
2009-04-03 21:16 ` Giorgio Mazzucchelli
2009-04-03 21:28 ` Luis R. Rodriguez
2009-04-03 21:31 ` Pavel Roskin
2009-04-03 21:44 ` Giorgio Mazzucchelli
2009-04-03 22:01 ` Luis R. Rodriguez [this message]
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=20090403220122.GF10278@tesla \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.