From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath11k@lists.infradead.org, Pradeep Chitrapu <pradeepc@qti.qualcomm.com>
Subject: Re: [PATCH v2 0/3] ath11k: Add Mesh mode support
Date: Wed, 29 May 2019 00:52:03 -0700 [thread overview]
Message-ID: <6ffbc8b675b1dbd6d8710fa604b5e507@codeaurora.org> (raw)
In-Reply-To: <1778145.5V7WxVhUSl@bentobox>
On 2019-05-29 00:41, Sven Eckelmann wrote:
> On Wednesday, 29 May 2019 06:26:16 CEST Rajkumar Manoharan wrote:
>> FW assert occurs, if a mesh node of different phymode/bw tries to join
>> existing mesh network. We noticed this issue when 11n device peering
>> with ath11k mesh
>> node. IMHO this shouldn't be HT/VHT specific. It is problem of mixed
>> mode.
>
> Happens for me when both HK01 boards are set up the same way (see the
> examples
> which I provided) in an earlier mail.
>
Will confirm it from our side too.
> Will check it again when I was informed that the new firmware is
> available for
> us.
>
Yes. Latest firmware release has fixes for secured 11s mode. You have to
cherrypick
ath11k changes[1] too.
-Rajkumar
[1] https://patchwork.kernel.org/project/ath11k/list/?series=124083
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-05-29 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 18:11 [PATCH v2 0/3] ath11k: Add Mesh mode support Rajkumar Manoharan
2019-04-19 18:11 ` [PATCH v2 1/3] ath11k: enable mesh mode Rajkumar Manoharan
2019-04-19 18:11 ` [PATCH v2 2/3] ath11k: allow 4 address transmission for mesh packet Rajkumar Manoharan
2019-04-19 18:11 ` [PATCH v2 3/3] ath11k: remove unnecessary check for PMF Rajkumar Manoharan
2019-05-28 13:48 ` [PATCH v2 0/3] ath11k: Add Mesh mode support Sven Eckelmann
2019-05-28 14:39 ` Sven Eckelmann
2019-05-29 4:26 ` Rajkumar Manoharan
2019-05-29 7:41 ` Sven Eckelmann
2019-05-29 7:52 ` Rajkumar Manoharan [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=6ffbc8b675b1dbd6d8710fa604b5e507@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=pradeepc@qti.qualcomm.com \
--cc=sven@narfation.org \
/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