From: Alexander Wilhelm <alexander.wilhelm@westermo.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: Jeff Johnson <jjohnson@kernel.org>,
ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: ath12k: REO status on PPC does not work
Date: Fri, 15 Aug 2025 14:00:00 +0200 [thread overview]
Message-ID: <aJ8hQKnlboOLFSkh@FUE-ALEWI-WINX> (raw)
In-Reply-To: <5ce28473-0fab-4fbe-9668-0042ff7d86c4@dd-wrt.com>
Am Fri, Aug 15, 2025 at 12:50:00PM +0200 schrieb Sebastian Gottschall:
> i just can say. the changes i had to make for ath11k to get big endian
> somwhat working where massive. alot of endian handling in ath11k is simply
> not considered. the firmware is little endian and alot of fields must be
> converted to host endian order. but at end end i struggled with dma
> transactions and gave up since it was not resolvable. the patch i made for
> ath11k was massive at the end and ath12k is not much different
> technically ath11k and ath12k can be merged at the end. i dont know why
> there are 2 drivers maintained which are technically very similar at the
> end. alot of patches for ath12k can be applied to ath11k which i do
> sometimes if its a usefull patch. but ath11k itself is abadoned for
> maintainance as it seems (at least if you look for qualcomm supplied
> patches)
Regarding the ath11k driver, sure, if the firmware doesn't handle the swap
correctly, it should be disabled and managed directly in the driver. I’ve
already have a patch for this, spanning over 10K lines, which I plan to
upstream at some point.
In contrast, the ath12k driver performs the swap internally from the beginning.
I only had to make a few minor changes to get a working ping. Some patches are
already in the queue, and others have already been merged upstream.
Best regards
Alexander Wilhelm
next prev parent reply other threads:[~2025-08-15 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 8:13 ath12k: REO status on PPC does not work Alexander Wilhelm
2025-08-15 9:55 ` Sebastian Gottschall
2025-08-15 10:26 ` Alexander Wilhelm
2025-08-15 10:50 ` Sebastian Gottschall
2025-08-15 12:00 ` Alexander Wilhelm [this message]
2025-08-19 6:38 ` Baochen Qiang
2025-08-19 6:59 ` Alexander Wilhelm
2025-08-19 7:26 ` Baochen Qiang
2025-08-19 8:10 ` Alexander Wilhelm
2025-08-19 9:21 ` Vasanthakumar Thiagarajan
2025-08-21 6:54 ` Alexander Wilhelm
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=aJ8hQKnlboOLFSkh@FUE-ALEWI-WINX \
--to=alexander.wilhelm@westermo.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.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.