From: Sven Eckelmann <sven@narfation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
Sven Eckelmann <seckelmann@datto.com>
Subject: Re: [PATCH 2/2] mac80211_hwsim: Register support for HE meshpoint
Date: Fri, 26 Jul 2019 15:31:02 +0200 [thread overview]
Message-ID: <3082836.hUm4yBdaKs@sven-edge> (raw)
In-Reply-To: <f2e16d10ce3eb3ff08c97c27424b824b8e012553.camel@sipsolutions.net>
[-- Attachment #1.1: Type: text/plain, Size: 1397 bytes --]
On Friday, 26 July 2019 15:26:32 CEST Johannes Berg wrote:
> On Wed, 2019-07-24 at 18:33 +0200, Sven Eckelmann wrote:
> > From: Sven Eckelmann <seckelmann@datto.com>
> >
> > Some features of 802.11ax without central organizing (AP) STA can also be
> > used in mesh mode. hwsim can be used to assist initial development of these
> > features without having access to HW.
> >
> > Signed-off-by: Sven Eckelmann <seckelmann@datto.com>
>
> Even with the tshark workaround in place, this breaks 68 mesh-related
> tests in hwsim tests. Jouni says only 3 use tshark ...
As I already wrote:
> The first three things looks like wpa_supplicant problems. Seems to be
> caused by the way HE forces VHT to be enabled and now the tests fail
> which try to disable VHT. There was already a patch [0] for that but it
> wasn't considered a good solution.
> But beside these three things there are various other problems in
> > wpa_supplicant regarding HE with pending patches. So I've used
> wpa_supplicant 91b6eba7732354ed3dfe0aa9715dc4c0746e3336 with two
> additional patches [1,2] and increased the VM memory to 1024 MB. Also
> wireshark (tshark to be more precise) had to be updated to
> v3.1.0rc0-1192-gf64990438c
[...]
> [0] https://patchwork.ozlabs.org/patch/1125305/
> [1] https://patchwork.ozlabs.org/patch/1125314/
> [2] https://patchwork.ozlabs.org/patch/1125322/
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
Sven Eckelmann <seckelmann@datto.com>
Subject: Re: [PATCH 2/2] mac80211_hwsim: Register support for HE meshpoint
Date: Fri, 26 Jul 2019 15:31:02 +0200 [thread overview]
Message-ID: <3082836.hUm4yBdaKs@sven-edge> (raw)
In-Reply-To: <f2e16d10ce3eb3ff08c97c27424b824b8e012553.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
On Friday, 26 July 2019 15:26:32 CEST Johannes Berg wrote:
> On Wed, 2019-07-24 at 18:33 +0200, Sven Eckelmann wrote:
> > From: Sven Eckelmann <seckelmann@datto.com>
> >
> > Some features of 802.11ax without central organizing (AP) STA can also be
> > used in mesh mode. hwsim can be used to assist initial development of these
> > features without having access to HW.
> >
> > Signed-off-by: Sven Eckelmann <seckelmann@datto.com>
>
> Even with the tshark workaround in place, this breaks 68 mesh-related
> tests in hwsim tests. Jouni says only 3 use tshark ...
As I already wrote:
> The first three things looks like wpa_supplicant problems. Seems to be
> caused by the way HE forces VHT to be enabled and now the tests fail
> which try to disable VHT. There was already a patch [0] for that but it
> wasn't considered a good solution.
> But beside these three things there are various other problems in
> > wpa_supplicant regarding HE with pending patches. So I've used
> wpa_supplicant 91b6eba7732354ed3dfe0aa9715dc4c0746e3336 with two
> additional patches [1,2] and increased the VM memory to 1024 MB. Also
> wireshark (tshark to be more precise) had to be updated to
> v3.1.0rc0-1192-gf64990438c
[...]
> [0] https://patchwork.ozlabs.org/patch/1125305/
> [1] https://patchwork.ozlabs.org/patch/1125314/
> [2] https://patchwork.ozlabs.org/patch/1125322/
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-26 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 16:33 [PATCH v5 0/4] mac80211/ath11k: HE mesh support Sven Eckelmann
2019-07-24 16:33 ` Sven Eckelmann
2019-07-24 16:33 ` [PATCH 1/2] mac80211: implement HE support for mesh Sven Eckelmann
2019-07-24 16:33 ` Sven Eckelmann
2019-07-24 16:33 ` [PATCH 2/2] mac80211_hwsim: Register support for HE meshpoint Sven Eckelmann
2019-07-24 16:33 ` Sven Eckelmann
2019-07-26 13:26 ` Johannes Berg
2019-07-26 13:26 ` Johannes Berg
2019-07-26 13:31 ` Sven Eckelmann [this message]
2019-07-26 13:31 ` Sven Eckelmann
2019-07-26 13:32 ` Johannes Berg
2019-07-26 13:32 ` Johannes Berg
2019-08-12 15:41 ` Sven Eckelmann
2019-08-12 15:41 ` Sven Eckelmann
2019-07-24 16:33 ` [PATCH v5 3/4] ath11k: register HE mesh capabilities Sven Eckelmann
2019-07-24 16:33 ` Sven Eckelmann
2019-07-24 16:33 ` [PATCH v5 4/4] ath11k: Disable SU support in meshpoint mode Sven Eckelmann
2019-07-24 16:33 ` Sven Eckelmann
2019-07-24 16:38 ` [PATCH v5 0/4] mac80211/ath11k: HE mesh support Sven Eckelmann
2019-07-24 16:38 ` Sven Eckelmann
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=3082836.hUm4yBdaKs@sven-edge \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=seckelmann@datto.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.