All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: lkml20120218@newton.leun.net,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: ath9k_htc: Issue with channel 52 and above (DFS?)
Date: Fri, 13 Jul 2012 15:35:27 +0200	[thread overview]
Message-ID: <5000241F.5050608@gmail.com> (raw)

Michael Leun wrote:

> ath9k_htc based card I see the same AP only if it operates on channel
> 36-48, I do NOT see it in iwlist scan results if it is on channel 52 to
> 140 - I again see it when it is on 149 or above.

This "Virgin Media" device, aka Netgear WNDA3200, is selling with a
world roaming regulatory domain = 0x65.

[ 1547.403743] ath: EEPROM regdomain: 0x65
[ 1547.403745] ath: EEPROM indicates we should expect a direct regpair map
[ 1547.403748] ath: Country alpha2 being used: 00
[ 1547.403750] ath: Regpair used: 0x65

And it's restricted *by the driver* to:

                 Frequencies:
                         * 5180 MHz [36] (30.0 dBm) (passive scanning, no IBSS)
                         * 5200 MHz [40] (30.0 dBm) (passive scanning, no IBSS)
                         * 5220 MHz [44] (30.0 dBm) (passive scanning, no IBSS)
                         * 5240 MHz [48] (30.0 dBm) (passive scanning, no IBSS)
                         * 5260 MHz [52] (30.0 dBm) (passive scanning, no IBSS, radar detection)
                         * 5280 MHz [56] (30.0 dBm) (passive scanning, no IBSS, radar detection)
                         * 5300 MHz [60] (30.0 dBm) (passive scanning, no IBSS, radar detection)
                         * 5320 MHz [64] (30.0 dBm) (passive scanning, no IBSS, radar detection)
                         * 5500 MHz [100] (disabled)
                         * 5520 MHz [104] (disabled)
                         * 5540 MHz [108] (disabled)
                         * 5560 MHz [112] (disabled)
                         * 5580 MHz [116] (disabled)
                         * 5600 MHz [120] (disabled)
                         * 5620 MHz [124] (disabled)
                         * 5640 MHz [128] (disabled)
                         * 5660 MHz [132] (disabled)
                         * 5680 MHz [136] (disabled)
                         * 5700 MHz [140] (disabled)
                         * 5745 MHz [149] (30.0 dBm) (passive scanning, no IBSS)
                         * 5765 MHz [153] (30.0 dBm) (passive scanning, no IBSS)
                         * 5785 MHz [157] (30.0 dBm) (passive scanning, no IBSS)
                         * 5805 MHz [161] (30.0 dBm) (passive scanning, no IBSS)
                         * 5825 MHz [165] (30.0 dBm) (passive scanning, no IBSS)

             reply	other threads:[~2012-07-13 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 13:35 Xose Vazquez Perez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-13  9:24 ath9k_htc: Issue with channel 52 and above (DFS?) Michael Leun

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=5000241F.5050608@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkml20120218@newton.leun.net \
    /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.