From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <peter.oh@bowerswilkins.com>
Cc: "Harms, Hannes" <hannes.harms@tu-bs.de>,
Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: mesh point and ap mode on same interface
Date: Wed, 15 Nov 2017 10:01:36 +0000 [thread overview]
Message-ID: <87po8jhncx.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <03700343-7b5c-b21e-8b7b-2ac8c7d3258b@bowerswilkins.com> (Peter Oh's message of "Wed, 8 Nov 2017 10:13:16 -0800")
(adding linux-wireless for a cfg80211 question)
Peter Oh <peter.oh@bowerswilkins.com> writes:
> On 11/08/2017 04:49 AM, Harms, Hannes wrote:
>
>> I found a solution for the problem:
>>
>> When joining the mesh with beacon interval set to 100
>> both mesh and ap interface are coming up.
>>
>> > iw mesh0 mesh join my_mesh beacon-interval 100
>>
>> The default beacon interval is 1000 for mesh interfaces.
>> It seems that QCA9880 is not working
>> with different beacon intervals for ap + mesh.
>
> Good to hear that working. But mesh beacon interval 1000 which is
> default value should work. Any mesh beacon intervals of multiple of AP
> beacon intervals are supposed to work.
>
> (In other words, mesh beacon intervals that are not aligned by
>multiple of AP beacon intervals won't work). These are valid for both
>of QCA9880 and QCA4019 as far as I know.
It would be nice if ath10k could print a warning if the beacon intervals
are not compatible. Or is there a way to enforce the beacon interval
with help of cfg80211 or mac80211?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-11-15 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 12:00 mesh point and ap mode on same interface Harms, Hannes
2017-10-06 16:52 ` Ben Greear
2017-10-06 18:18 ` Peter Oh
2017-10-09 8:47 ` Harms, Hannes
[not found] ` <CADjYELwdUxEap_z=_HD4DS4FEQ2_2HP3w9cvDU-BTFLoOTDipg@mail.gmail.com>
[not found] ` <5c04c7fe-8cf8-ddd8-d6a7-f42629586a63@bowerswilkins.com>
2017-10-09 19:14 ` Peter Oh
[not found] ` <067d234a-59f0-4175-55af-9354617057b9@tu-bs.de>
2017-10-11 18:10 ` Peter Oh
2017-11-08 12:49 ` Harms, Hannes
2017-11-08 18:13 ` Peter Oh
2017-11-15 10:01 ` Kalle Valo [this message]
2017-11-15 10:13 ` Arend van Spriel
2017-11-15 10:27 ` Kalle Valo
2017-11-15 10:36 ` Arend van Spriel
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=87po8jhncx.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=hannes.harms@tu-bs.de \
--cc=linux-wireless@vger.kernel.org \
--cc=peter.oh@bowerswilkins.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