Return-path: Received: from mail-io0-f177.google.com ([209.85.223.177]:33085 "EHLO mail-io0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756551AbdEUPnh (ORCPT ); Sun, 21 May 2017 11:43:37 -0400 Received: by mail-io0-f177.google.com with SMTP id p24so69167868ioi.0 for ; Sun, 21 May 2017 08:43:37 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Krishna Chaitanya Date: Sun, 21 May 2017 21:13:16 +0530 Message-ID: (sfid-20170521_174503_987722_AFBA0F9B) Subject: Re: ath10k: controlling TX aggregation To: Ben Greear Cc: linux-wireless , ath10k Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: On Sun, May 21, 2017 at 8:36 PM, Ben Greear wrote: > > > On 05/20/2017 09:21 AM, Krishna Chaitanya wrote: >> >> On Mon, May 15, 2017 at 3:02 PM, Krishna Chaitanya >> wrote: >>> >>> On Fri, May 12, 2017 at 8:15 PM, Ben Greear >>> wrote: >>>> >>>> What chipset, and what firmware version? >>>> >>>> Thanks, >>>> Ben >>> >>> >>> Hi Ben, >>> >>> I have missed your response. PFB details. >>> >>> chip: QCA986x/988x PCIe >>> FW ver: 10.2.4.70.54 api 5 >>> kernel: 4.11.0-rc+7 (wireless-drivers-next) >>> >> Ben, >> >> any clues? > > > I haven't tried that test yet, and use a different > firmware version. I did recently work on allowing larger > AMSDU aggregates and have that working in my CT firmware and > driver. ok, so at least its suppose to work.