public inbox for ath11k@lists.infradead.org
 help / color / mirror / Atom feed
From: Stefan Zegenhagen <stefan.zegenhagen@azg-tech.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k: IPQ6018: support for 802.11s MESH
Date: Tue, 09 Jul 2024 10:24:15 +0200	[thread overview]
Message-ID: <196d7fb9f411cbfad0c8cf690efcf55da01469c0.camel@azg-tech.com> (raw)
In-Reply-To: <87frsjdhzn.fsf@kernel.org>

Dear Kalle, dear all,

I can understand your concern regarding unknown patches. I've checked
carefully that there's no OpenWRT patch on the ath11k driver that could
possibly cause this behaviour. Most patches are vanilla kernel
backports, others do harmless things like
 - disabling coldboot calibration on IPQ6018
 - setting FW memory mode via DTB
 - tweaking QRTR instance IDs to allow multiple ath11k cards to be used

However, vanilla kernel still requires numerous patches to actually
work on the Mango board. So it's difficult to test without any patches,
since the IPQ6018 is a built-in AHB core and I cannot simply plug it
somewhere else.

Could you please at least answer the question whether mesh is supposed
to be working on IPQ6018 with vanilla kernel, which firmware version is
required and whether it is required to enable raw mode data path? Is
there some knowledge around? With ath10k, there was at least a WMI
services file in debugfs and a feature list in the 'bin' file. Both are
no longer available and I can no longer see anything about firmware
capabilities.


Kind regards,
Stefan


Am Montag, dem 08.07.2024 um 18:24 +0300 schrieb Kalle Valo:
> 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.
> 


  reply	other threads:[~2024-07-09  8: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
2024-07-09  8:24   ` Stefan Zegenhagen [this message]
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=196d7fb9f411cbfad0c8cf690efcf55da01469c0.camel@azg-tech.com \
    --to=stefan.zegenhagen@azg-tech.com \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.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