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
