From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org
Subject: Re: [RFC PATCH] ath11k: register HE mesh capabilities
Date: Mon, 03 Jun 2019 17:20:49 +0200 [thread overview]
Message-ID: <4287292.mqGLfAt13s@bentobox> (raw)
In-Reply-To: <20190603151719.31974-1-sven@narfation.org>
[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]
On Monday, 3 June 2019 17:17:19 CEST Sven Eckelmann wrote:
> From: Sven Eckelmann <seckelmann@datto.com>
>
> The capabilities for the HE mesh are generated from the capabilities
> reported by the fw. But the firmware only reports the overall capabilities
> and not the one which are specific for mesh. Some of them (TWT, MU UL/DL,
> TB PPDU, ...) require an infrastructure setup with a main STA (AP)
> controlling the operations. This is not the case for mesh and thus these
> capabilities are removed from the list of capabilities.
>
> Signed-off-by: Sven Eckelmann <seckelmann@datto.com>
> ---
> drivers/net/wireless/ath/ath11k/mac.c | 56 +++++++++++++++++++++++++++
> 1 file changed, 56 insertions(+)
This patch is just for demonstration purposes. It requires the
patch(es| series):
* https://patchwork.kernel.org/cover/10963863/ (whole series)
* https://patchwork.kernel.org/patch/10963219/
* https://patchwork.kernel.org/patch/10963221/
But the firmware WLAN.HK.2.1.0.1-00629-QCAHKSWPL_SILICONZ-1 seems to hang when
trying to associate.
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
prev parent reply other threads:[~2019-06-03 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 15:17 [RFC PATCH] ath11k: register HE mesh capabilities Sven Eckelmann
2019-06-03 15:20 ` Sven Eckelmann [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=4287292.mqGLfAt13s@bentobox \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.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