From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH v2 0/3] ath11k: Add Mesh mode support
Date: Tue, 28 May 2019 21:26:16 -0700 [thread overview]
Message-ID: <09bc6205f3f65f60c12613555fdba695@codeaurora.org> (raw)
In-Reply-To: <3594678.I98WQv5yxB@bentobox>
On 2019-05-28 07:39, Sven Eckelmann wrote:
> On Tuesday, 28 May 2019 15:48:25 CEST Sven Eckelmann wrote:
> [...]
>> What else is required to get this working? I used ath11k-bringup
>> (which
>> included these patches) and wanted to implement the HE registration
>> part for
>> it. But it turns out that it doesn't event work here with VHT. This is
>> what
> I
>> did on two HK01 rev B:
> [...]
>
> Just talked to John. It seems that mesh at the moment only "works" when
> using
> legacy (non-HT) mode (this is what he used previously - so mesh join
> without
> freq and bandwidth):
>
> iw phy phy2 interface add mesh2 type mp
> ip link set up dev mesh2
> iw dev mesh2 mesh join testmesh
>
> But the HT/VHT stuff is just crashing the firmware as shown in the last
> mail.
>
> iw dev mesh2 mesh join testmesh freq 5180 80MHz
>
> Also tested ph1 with "freq 2412 HT20" and it crashed the same way.
>
Sven,
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.
-Rajkumar
-Rajkumar
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-05-29 4:26 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 [this message]
2019-05-29 7:41 ` Sven Eckelmann
2019-05-29 7:52 ` Rajkumar Manoharan
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=09bc6205f3f65f60c12613555fdba695@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--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 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.