All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Harms, Hannes" <hannes.harms@tu-bs.de>
To: ath10k@lists.infradead.org
Subject: Unable to set channel above 100 with latest CT Kernel and Firmware
Date: Mon, 17 Aug 2015 13:06:23 +0200	[thread overview]
Message-ID: <55D1C02F.4010005@tu-bs.de> (raw)
In-Reply-To: <1439738757-29199-4-git-send-email-me@bobcopeland.com>


Hi,

I am trying to set up the latest Kernel (4.2rc6) and firmware 
(10.1.467-ct-14) form Candela for a 5Ghz network.
Unfortunately I am not able to set channels above 100, although 
regulatory domain is set to DE.
Maybe someone has an advice what is going wrong?

Regards
Hannes

My configuration:

Debian with Kernel 4.2-rc6  form Candela (self compiled)
Firmware: 10.1.467-ct-14

iw reg get
country DE: DFS-ETSI
     (2400 - 2483 @ 40), (N/A, 20), (N/A)
     (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
     (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
     (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
     (57000 - 66000 @ 2160), (N/A, 40), (N/A)

iw list
     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) (no IR, radar detection)
               DFS state: usable (for 550 sec)
               DFS CAC time: 60000 ms
             * 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
               DFS state: usable (for 550 sec)
               DFS CAC time: 60000 ms
             * 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
               DFS state: usable (for 550 sec)
               DFS CAC time: 60000 ms
             * 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
               DFS state: usable (for 550 sec)
               DFS CAC time: 60000 ms
             * 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)
             * 5720 MHz [144] (disabled)
             * 5745 MHz [149] (disabled)
             * 5765 MHz [153] (disabled)
             * 5785 MHz [157] (disabled)
             * 5805 MHz [161] (disabled)
             * 5825 MHz [165] (disabled)


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2015-08-17 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 15:25 [PATCH 0/3] ath10k mesh support Bob Copeland
2015-08-16 15:25 ` [PATCH 1/3] ath10k: enable monitor when OTHER_BSS requested Bob Copeland
2015-08-16 15:25 ` [PATCH 2/3] ath10k: check for encryption before adding MIC_LEN Bob Copeland
2015-08-16 15:25 ` [PATCH 3/3] ath10k: implement mesh support Bob Copeland
2015-08-17 11:06   ` Harms, Hannes [this message]
2015-08-18 11:54     ` Unable to set channel above 100 with latest CT Kernel and Firmware Kalle Valo
2015-08-18 14:52       ` Ben Greear
2015-08-18 11:50 ` [PATCH 0/3] ath10k mesh support Kalle Valo
2015-08-18 12:42   ` Bob Copeland
2015-08-18 16:04     ` 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=55D1C02F.4010005@tu-bs.de \
    --to=hannes.harms@tu-bs.de \
    --cc=ath10k@lists.infradead.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.