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 12:26:42 +0200 [thread overview]
Message-ID: <aJ8LYj+NGaX8cwge@FUE-ALEWI-WINX> (raw)
In-Reply-To: <573c76a8-c2a0-4b9c-b5a8-762b8d094b81@dd-wrt.com>
Am Fri, Aug 15, 2025 at 11:55:14AM +0200 schrieb Sebastian Gottschall:
> i played already with big endian platforms and ath11k (not ath12k) for
> months. there is also a problem with the dma descriptors. the firmware
> simply doesnt support big endian with host communication at the end even if
> there is a endian flag for the firmware. dont get into this rabit hole. (i
> worked 3 months on it and gave up)
> at the end (i was working on a cavium octeon platform at that time) i just
> switched the kernel boot to little endian which is possible on many ppc
> platforms too.
The 'ath11k' driver works a bit differently. The endian swap is implemented in
the firmware and was never properly tested. My investigations show that the
firmware does not handle the swap consistently. According to 'kvalo', different
firmware versions treat the swap differently. See [1].
With 'ath12k', the situation looks better. Unfortunately, there are still some
memcpys from u32 to u8 or similar. Also, reading from DMA memory is not swapped.
I already have ath12k running, I get ping responses and can transmit data.
However, not in all modes, and there are still some bugs I’m trying to iron out.
Best regards
Alexander Wilhelm
---
[1] https://lore.kernel.org/ath11k/68290980-5bfb-c88c-be78-954f9591c135@westermo.com/T/#u
next prev parent reply other threads:[~2025-08-15 10:36 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 [this message]
2025-08-15 10:50 ` Sebastian Gottschall
2025-08-15 12:00 ` Alexander Wilhelm
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=aJ8LYj+NGaX8cwge@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox