ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Marble <tmarble@info9.net>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: Tom Marble <tmarble@info9.net>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Cannot initialize Compex WLE600VX for 802.11ac?
Date: Wed, 22 Jun 2016 08:10:34 -0500	[thread overview]
Message-ID: <57dd1n9mks5.fsf@cerise.info9.net> (raw)
In-Reply-To: <87y45xiuts.fsf@kamboji.qca.qualcomm.com>

"Valo, Kalle" <kvalo@qca.qualcomm.com> writes:
> Do you have CONFIG_ATH10K_DFS_CERTIFIED enabled?

No.. the option isn't even commented out in my .config??
Is there are tree other than...
  git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git

> Also check that that
> regulatory is correct with 'iw reg get' and 'iw phy0 info', especially
> that 80 MHz channels are supported.

root@six:/# iw reg get
country US: DFS-FCC
        (2402 - 2472 @ 40), (N/A, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 17), (N/A)
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
        (5735 - 5835 @ 80), (N/A, 30), (N/A)
        (57240 - 63720 @ 2160), (N/A, 40), (N/A)
root@six:/#

(I cannot run 'iw phy0 info' at the moment as I'm away from the lab)

> Also I would try first without DFS on channel 36 just to make it easier
> to pinpoint the problem.

Okay, thanks!

--Tom

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

  reply	other threads:[~2016-06-22 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 14:42 Cannot initialize Compex WLE600VX for 802.11ac? Tom Marble
2016-06-22  6:47 ` Valo, Kalle
2016-06-22 13:10   ` Tom Marble [this message]
2016-06-22 14:08     ` Valo, Kalle
2016-06-23 13:00       ` Tom Marble
2016-06-23 13:27         ` Tomasz Skapski
2016-06-24  3:27           ` Tom Marble
2016-06-27 11:52             ` Michal Kazior
2016-06-27 12:42               ` Tom Marble

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=57dd1n9mks5.fsf@cerise.info9.net \
    --to=tmarble@info9.net \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox