QoS Control Field Stripped Off

[Michal Kazior]

On 19 February 2014 09:45, Yeoh Chun-Yeow <yeohchunyeow at gmail.com> wrote:
>> Did you remove the call to ath10k_tx_h_qos_workaround() in ath10k_tx()?
> Yes. I disable this.
>
>> Did you get any htt tx completion for the frame (look for `htt tx
>> completion msdu_id` and `htt tx alloc msdu_id` in traces/logs)? What
>> was the status of it?
> Try to capture using wireshark and no Tx frames. The following log observed:
>
> [  272.340000] ath10k: htt rx, msg_type: 0x1
> [  272.340000] ath10k: htt rx mgmt ctrl
> [  272.340000] ath10k: htt tx alloc msdu_id 0
> [  272.340000] ath10k: tx-msdu 0x71e2e10
> [  272.340000] ath10k: htt data tx using tid 0
> [  272.340000] ath10k: htt data tx not mgmt [additional log to
> indicate data and not mgmt]
> [  272.340000] ath10k: htt rx, msg_type: 0x7
> [  272.340000] ath10k: htt tx completion num_msdus 1
> [  272.340000] ath10k: htt tx completion msdu_id 0 discard 0 no_ack 0
> [  272.340000] ath10k: htt tx free msdu_id 0
>
> So, FW drops the Tx raw frame, even though the htt tx indicates completion?

This might be HW itself as well. I'm adding Ben to the discussion.

Ben: You've done some research on tx/rx in firmware to get software
encryption in ath10k going, right? Did you play with raw tx format or
see any obstacles in the code that could prevent it from working?


Michał