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: Wed, 10 Jul 2024 13:43:18 +0300	[thread overview]
Message-ID: <87cynlbk8p.fsf@kernel.org> (raw)
In-Reply-To: <196d7fb9f411cbfad0c8cf690efcf55da01469c0.camel@azg-tech.com> (Stefan Zegenhagen's message of "Tue, 09 Jul 2024 10:24:15 +0200")

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

> 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

So there are changes to ath11k and mac80211?

> 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.

Sure, I understand that. But we have been bitten by distro changes so
many times in the past that we simply don't have time to support them.

> 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.

I have not tested mesh mode myself with IPQ6018 but I did saw a report
claiming that at least this firmware has working mesh mode:

https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/tree/main/IPQ6018/hw1.0/2.6.0.1/WLAN.HK.2.6.0.1-01291-QCAHKSWPL_SILICONZ-1?ref_type=heads

Though that's not the most reliable source so I'm taking the report as a
grain of salt.

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

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


  reply	other threads:[~2024-07-10 10:43 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
2024-07-10 10:43     ` Kalle Valo [this message]
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=87cynlbk8p.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