From: Ben Greear <greearb@candelatech.com>
To: Fraser Cadger <frasercadger@gmail.com>, ath10k@lists.infradead.org
Subject: Re: Multiple simultaneous channels on QCA9882
Date: Mon, 10 Sep 2018 09:06:36 -0700 [thread overview]
Message-ID: <bc1f526c-91a9-4d1e-50fc-00f5b60774d8@candelatech.com> (raw)
In-Reply-To: <CAKc-1SD6VF8-2O=Od+iDjc2wbB3-rSuXy9J63S8xx2w4GHfi3Q@mail.gmail.com>
On 09/10/2018 07:37 AM, Fraser Cadger wrote:
> Hi,
>
> I am using a device based on the Atheros QCA9882 chipset.
>
> I would like to make use of the simultaneous dual-band functionality
> that the device provides. The goal is to have to interfaces with one
> acting as
> an Access Point (wlan0) and the other acting as a client of another AP
> (wlan1). Ideally, both of these interfaces should be operating on
> different channels.
These radios can support both bands, but at any given time, they can be on
only a single channel. You need multiple radios to run on multiple channels.
Thanks,
Ben
>
> As I have understood it, Atheros/Qualcomm market the QCA9882 as being
> capable of both dual-band and concurrent operation:
> https://www.qualcomm.com/news/releases/2012/02/23/qualcomm-atheros-launches-80211ac-product-ecosystem-provide-end-end-gigabit
>
> I am using v4.1 of the Linux kernel.
>
> Having experienced some difficulties using hostapd and wpa_supplicant,
> I checked the device capabilities using iw. If I am interpreting the
> output below correctly, it is only possible to use 1 channel on both
> interfaces:
>
> valid interface combinations:
> * #{ managed, P2P-client } <= 36, #{ P2P-GO } <= 3,
> #{ AP } <= 7, #{ IBSS } <= 1,
> total <= 36, #channels <= 1, STA/AP BI must match
>
>
> As I understand it, #channels <=1 indicates that only 1 channel may be
> used at a particular time by all interfaces.
>
> I am wondering if this is a limitation of the driver, or if there has
> been a misunderstanding in the capabilities of the hardware.
>
> Does anyone have experience with this?
>
> Regards,
>
> Fraser
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-09-10 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:37 Multiple simultaneous channels on QCA9882 Fraser Cadger
2018-09-10 16:06 ` Ben Greear [this message]
2018-09-11 8:54 ` Fraser Cadger
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=bc1f526c-91a9-4d1e-50fc-00f5b60774d8@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=frasercadger@gmail.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