Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark

Michal Kazior michal.kazior at tieto.com
Tue Feb 16 07:17:55 PST 2016

On 16 February 2016 at 16:02, Lindner, Frank <Frank.Lindner at ghmt.de> wrote:
> Hi Michal,
> thanks for your instant response.
> May I ask why this isn't implemented in a new firmware release?

I don't know.

The patch I've pointed out uses a hacky approach by using firmware
debugging interface to get the tx rate info. Because of that it
carries an inherent performance degradation.

> Is there a short manual, what and where I need to edit the code and how to compile it? I'm not that familiar with coding on that level.

Hmm.. The least painful and fairly documented procedure would be to
use backports:


You'll then need to port the changes from the pointed patch into
there. Note: chromium uses `wireless-xxx` masking. You'll need to make
sure you apply changes to drivers/net/wireless/ath/ath10k directory.

Here's a few words on the diff format used for patches:



> Thanks.
> Best Regards,
> Frank
> -----Ursprüngliche Nachricht-----
> Von: Michal Kazior [mailto:michal.kazior at tieto.com]
> Gesendet: Dienstag, 16. Februar 2016 15:46
> An: Lindner, Frank
> Cc: ath10k at lists.infradead.org
> Betreff: Re: Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark
> On 16 February 2016 at 15:33, Lindner, Frank <Frank.Lindner at ghmt.de> wrote:
>> Hi there,
>> I'm using QCA980 hw2.0 (Compex WLE900VX5) in monitor mode. Using Linux Kernel 4.3.3 and ath10k firmware
>> When capturing 2.4 GHz WIFI operating in 802.11g (1 to 54 Mbit/s), Wireshark displays only 1, 2, 5.5 or 11 Mbit/s as TX rate for the frames. When capturing in parallel with Airpcap on Windows or a Ralink-based card in monitor mode, frame TX rate is displayed correctly with 1 to 54 Mbit/s.
>> I also tried older firmware versions. Same issue.
>> Also when trying to capture with tcpdump, only up 11 Mbit/s is shown.
>> Is this a known issue?
>> Is there any fix for this?
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k#known_bugslimitations
> If you don't mind dirtying your hands with some C code you can try using the following patch (it will not cleanly apply to upstream kernel but should be fairly straightforward to port):
>   https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-checkins/YGYm6gNUnEE
> Michał
> Vorstandsvorsitzender: Dipl.-Ing. Dirk Wilhelm
> Aufsichtsratsvorsitzender: Dr.-Ing. Peter Hasse
> Handelsregister: HRB Saarbrücken Nr. 13201
> Ust.ID Nr.: DE 153807627

More information about the ath10k mailing list