Frames acknowledged and silently discarded in firmware

Hi, We have observed a problem where, under certain conditions, the ath10k firmware will acknowledge frames but not send them up to the driver. Frames are sent by a mesh access point (MAP1) to a second mesh AP (MAP2) at MCS 9/NSS-3, which at that distance is probably marginal. Since frames

[PATCH] Revert "ath10k: add sanity check to ie_len before parsing fw/board ie"

From: Ryan Hsu This reverts commit 9ed4f91628737c820af6a1815b65bc06bd31518f. The commit introduced a regression that over read the ie with the padding. - the expected IE information ath10k_pci :03:00.0: found firmware features ie (1 B) ath10k_pci :03:00.0:

Re: ath10k: correct the length of DRAM dump for QCA6174 hw3.x/QCA9377 hw1.1

Yu Wang wrote: > The length of DRAM dump for QCA6174 hw3.0/hw3.2 and QCA9377 hw1.1 > are less than the actual value, some coredump contents are missed. > To fix it, change the length from 0x9 to 0xa8000. > > Fixes: 703f261dd77f ("ath10k: add memory dump support for

Re: [v3,1/2] pci: Add vendor id of Ubiquiti Networks

Tobias Schramm wrote: > Acked-by: Bjorn Helgaas > Signed-off-by: Tobias Schramm > Signed-off-by: Kalle Valo 2 patches applied to ath-current branch of ath.git, thanks. d5cc61119343 PCI: Add Ubiquiti

Re: ath10k: fix kernel panic issue during pci probe

Yu Wang wrote: > If device gone during chip reset, ar->normal_mode_fw.board is not > initialized, but ath10k_debug_print_hwfw_info() will try to access its > member, which will cause 'kernel NULL pointer' issue. This was found > using a faulty device (pci link went down

Re: [PATCH] Revert "ath10k: add sanity check to ie_len before parsing fw/board ie"

On 7 February 2018 at 13:51, Kalle Valo wrote: > From: Ryan Hsu > > This reverts commit 9ed4f91628737c820af6a1815b65bc06bd31518f. > > The commit introduced a regression that over read the ie with > the padding. > > - the expected IE information > >