public inbox for ath11k@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Stefan Zegenhagen <stefan.zegenhagen@azg-tech.com>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: IPQ6018: support for 802.11s MESH
Date: Mon, 08 Jul 2024 18:24:28 +0300	[thread overview]
Message-ID: <87frsjdhzn.fsf@kernel.org> (raw)
In-Reply-To: <3581dfd05dd3468d97b3fd06072d206732da9482.camel@azg-tech.com> (Stefan Zegenhagen's message of "Mon, 08 Jul 2024 14:44:34 +0200")

Stefan Zegenhagen <stefan.zegenhagen@azg-tech.com> writes:

> Dear all,
>
> I've got an 8devices Mango board here with an IPQ6018 WiFi6 built-in
> via AHB and running kernel 6.6.35 with OpenWRT patches and firmware
> WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3.
>
> Somehow I can't get mesh support running as it should. Tried loading
> ath11k with frame_mode=1 which leads to association via MGMT frames
> working fine but afterwards no more frames are received and associated
> peers time out.
>
> When loading ath11k with frame_mode=0 (raw), association works well and
> afterwards I'm able to transmit frames with sufficient rates, but RX
> hardly works and spews loads of kernel messages.
>
> Is mesh supposed to be working at all with ath11k cards? (See below for
> more info.)

We can't give distro support, we only support kernel.org. If you are
using OpenWrt patches you should ask them, we don't know what changes
there are.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-07-08 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 12:44 ath11k: IPQ6018: support for 802.11s MESH Stefan Zegenhagen
2024-07-08 15:24 ` Kalle Valo [this message]
2024-07-09  8:24   ` Stefan Zegenhagen
2024-07-10 10:43     ` Kalle Valo
2024-07-10 11:16       ` Stefan Zegenhagen
2024-07-10 11:34         ` Kalle Valo
2024-07-11  9:44           ` Stefan Zegenhagen

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=87frsjdhzn.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=stefan.zegenhagen@azg-tech.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