From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Harms, Hannes" <hannes.harms@tu-bs.de>
Cc: ath10k@lists.infradead.org
Subject: Re: Unable to set channel above 100 with latest CT Kernel and Firmware
Date: Tue, 18 Aug 2015 14:54:29 +0300 [thread overview]
Message-ID: <874mjwdd6y.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <55D1C02F.4010005@tu-bs.de> (Hannes Harms's message of "Mon, 17 Aug 2015 13:06:23 +0200")
"Harms, Hannes" <hannes.harms@tu-bs.de> writes:
> 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?
Btw, please don't hijack threads (ie. reply to an existing thread and
change subject) as it confuses patchwork[1]. Instead start a new thread.
[1] https://patchwork.kernel.org/patch/7023511/
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-08-18 11:54 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 ` Unable to set channel above 100 with latest CT Kernel and Firmware Harms, Hannes
2015-08-18 11:54 ` Kalle Valo [this message]
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=874mjwdd6y.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=hannes.harms@tu-bs.de \
/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.