From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Li Sun <lsun3@buffalo.edu>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Cannot use 80MHz channel
Date: Wed, 18 Dec 2013 08:59:19 +0200 [thread overview]
Message-ID: <87ppoubq60.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=hnirSQhgydH9DQdx+1A3WUV+gMUCMOQGP8yvew8jF-g@mail.gmail.com> (Michal Kazior's message of "Wed, 18 Dec 2013 07:15:00 +0100")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 17 December 2013 22:51, Li Sun <lsun3@buffalo.edu> wrote:
>> Hi,
>>
>> I am trying to play around with the ath10k driver. I have two Qualcomm
>> Atheros QCA9880 Version 2 802.11ac chipsets. I put one of the cards in
>> AP mode using hostapd and connect the other one as a client.
>>
>> I am using the hostapd config mentioned at
>> "wireless.kernel.org/en/users/Drivers/ath10k/configuration". The
>> client connects but the throughput is just around 300 Mbps (suggesting
>> 40 MHz channel-width) and NOT any higher. It seems I am unable to use
>> the 80 MHz channel-width. Also, when I checked the kernel logs
>> (dmesg), I found the following message on the client side only:
>>
>> capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
>>
>>
>> Could this problem be related to CRDA ? I am in the US.
>
> Check output of `iw reg get`. If you see no entries with `@ 80` you
> have to upgrade your regdb.
And the easiest way to do that (if you compile your own kernels) is to
enable CONFIG_CFG80211_INTERNAL_REGDB and copy db.txt from
wireless-regdb to net/wireless/db.txt.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2013-12-18 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 21:51 Cannot use 80MHz channel Li Sun
2013-12-18 6:15 ` Michal Kazior
2013-12-18 6:59 ` Kalle Valo [this message]
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=87ppoubq60.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=lsun3@buffalo.edu \
--cc=michal.kazior@tieto.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.