From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Mohammed Shafi <shafi.wireless@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k 9380: All 5Ghz channels flagged as passive-scanning
Date: Mon, 23 May 2011 14:42:53 -0700 [thread overview]
Message-ID: <BANLkTinrM1oBfKUoCzs9_DOw+EmpW=ikig@mail.gmail.com> (raw)
In-Reply-To: <4DDAD3D5.1070001@candelatech.com>
On Mon, May 23, 2011 at 2:38 PM, Ben Greear <greearb@candelatech.com> wrote:
> On 05/23/2011 02:28 PM, Luis R. Rodriguez wrote:
>>
>> On Mon, May 23, 2011 at 2:19 PM, Ben Greear<greearb@candelatech.com>
>> wrote:
>
>>> Since it *is* possible to start an AP on a channel with existing AP,
>>> I assume that the NIC must be able to handle this properly..or is
>>> that ability to start on a scanned channel just a bug? (Please
>>> don't fix it, if it is :P)
>>
>> It a feature, AP functionality is allowed on that channel on a world
>> roaming card given that no CTL is present so the lower regulatory
>> value, from CRDA, is used instead of the CTL value.
>
> So as long as you have a functional CRDA and do not mis-represent
> your country with 'iw reg set',
Atheros cards have an EEPROM value for a regulatory domain which is
always used, regardless of what you tell cfg80211 with 'iw reg set',
'iw reg set' will just help compliance further.
> is there any way to
> actually get the system out of spec if you use "eeprom" reg-domain of 0x0?
No. You can only do this by trying to take the card out of compliance
purposely or unknowingly in software.
Luis
next prev parent reply other threads:[~2011-05-23 21:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 22:22 ath9k 9380: All 5Ghz channels flagged as passive-scanning Ben Greear
2011-05-23 11:28 ` Mohammed Shafi
2011-05-23 16:54 ` Ben Greear
2011-05-23 18:39 ` Ben Greear
2011-05-23 18:52 ` Ben Greear
2011-05-23 19:26 ` Luis R. Rodriguez
2011-05-23 20:09 ` Ben Greear
2011-05-23 20:25 ` Luis R. Rodriguez
2011-05-23 20:51 ` Ben Greear
2011-05-23 20:59 ` Luis R. Rodriguez
2011-05-23 21:19 ` Ben Greear
2011-05-23 21:28 ` Luis R. Rodriguez
2011-05-23 21:38 ` Ben Greear
2011-05-23 21:42 ` Luis R. Rodriguez [this message]
2011-05-23 21:46 ` Luis R. Rodriguez
2011-05-23 21:59 ` Ben Greear
2011-05-23 22:15 ` Luis R. Rodriguez
2011-05-24 4:48 ` Ben Greear
2011-05-24 11:33 ` Luis R. Rodriguez
2011-05-24 13:00 ` Brian Prodoehl
2011-05-24 13:11 ` Luis R. Rodriguez
2011-05-24 13:18 ` Brian Prodoehl
2011-05-24 21:39 ` Luis R. Rodriguez
2011-05-24 14:06 ` Mohammed Shafi
2011-05-24 14:08 ` Mohammed Shafi
2011-05-24 15:05 ` Ben Greear
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='BANLkTinrM1oBfKUoCzs9_DOw+EmpW=ikig@mail.gmail.com' \
--to=mcgrof@gmail.com \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=shafi.wireless@gmail.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 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.