Ath10k HTT driver - whats is behind HTT?

Hi.

I have well known CT driver issues with my R7800 and tried different firmwares. I saw that there is also a HTT version but I did not find any information about it. In LuCi it shows also a much higher transmission power of 26dBm...does anyone know what is behind it? Also my TP-Link Archer 6CV2 has this with standard ath10k CT driver, my R7800 not...(23dDm)?? But chipset is different...

  • Using newest stable OpenWrt 21.02.2 r16495-bf0c965af
  • Found some article that there is a bandwidth where higher 5Ghz power is allowed on specific channels....perhaps its that...
  • What is the HTT driver for?

Cheers,
Nils

http://candelatech.com/ath10k-10.4.php
(scroll down a bit)

See also Candela's git hub issues such as the post quoted below or inspect the ath10k-ct driver source. You'll find additional detail there; however the details are technical and mostly beyond my current level of understanding.

I take the advice below and use the htt firmware variant pretty much exclusively.

Use HTT mgt firmware, it puts managements frames over the normal data frame transport (HTT protocol in the driver), and this lets management frames scale better, especially in cases where there are lots of connections.

If using ath10k-ct driver (which is suggested), then the suggested firmware variant is: **firmware-5-ct-htt-mgt-community** .

It’s running fine here also and I found this comment in the page linked. But why is htt version not OpenWRT standard if it is recommended by CT?

Possibly because not all chipsets support ct-htt.

For example, mine (qca988x) supports ct-full-htt, but not ct-htt.

Which is better to use for which case? ct-full-htt or ct-htt? I have an Archer C60 with 64MB of RAM.

Given the 64MB memory, I'd suggest not using full-htt.

Sorry to necro, but I was searching around for HTT info and this thread was the only relevant one. Some more info from the Candela link:

Enable CT Management-over-HTT firmware variants. These are NOT compatible with stock drivers. Stock 10.4 has somewhat similar HTT mgt API already, so this is mostly to be compatible with earlier firmware and to make sure all frames go through the same code path instead of using the MGT specific packet-transmit API that stock firmware uses.

Here's some code, comments, and version history I found:
https://android.googlesource.com/kernel/msm-modules/wlan-fw-api/+/refs/tags/android-10.0.0_r0.66/fw/htt.h#31
https://android.googlesource.com/kernel/msm-modules/wlan-fw-api/+/refs/tags/android-10.0.0_r0.66/fw/htt_common.h#96

Unfortunately I can't use the 5GHz band anymore because they broke ath10k and ath10k-ct. More info here.