From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail2.candelatech.com ([208.74.158.173]) by merlin.infradead.org with esmtp (Exim 4.85_2 #1 (Red Hat Linux)) id 1b9zjP-0005pv-BW for ath10k@lists.infradead.org; Mon, 06 Jun 2016 18:58:35 +0000 Subject: Re: Any tips on where per-packet antenna selection could be pushed? References: <5755B0FF.9010900@candelatech.com> <5755B2D9.7080207@candelatech.com> <5755BABA.1030006@candelatech.com> From: Ben Greear Message-ID: <5755C7AF.6020203@candelatech.com> Date: Mon, 6 Jun 2016 11:57:51 -0700 MIME-Version: 1.0 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Zach Sherin , Adrian Chadd Cc: ath10k@lists.infradead.org On 06/06/2016 11:48 AM, Zach Sherin wrote: > Interesting. Could I ask if there's somewhere I should start digging? > If it's not obvious I'm a driver/kernel newbie, but I'm happy to > learn. Should I start by going through ath10k's documentation/code > until I find the relevant bits? Unfortunately, without firmware source, you have probably no chance to do this. And, you also probably have about no chance of getting firmware source. Thanks, Ben > > Thanks, > Zach > > > On Mon, Jun 6, 2016 at 2:42 PM, Adrian Chadd wrote: >> I bet the ruckus mode shift stuff is in the ath10k hardware and is >> configurable per TX descriptor. >> >> a >> >> On Jun 6, 2016 11:03 AM, "Ben Greear" wrote: >>> >>> On 06/06/2016 10:59 AM, Zach Sherin wrote: >>>> >>>> I was aiming to run this off a serial interface on the general board, >>>> not on the ath10k NIC. I have a consumer QCA9880 PCI board in an >>>> Archer C7 router. It would be awesome if I could steal a GPIO or >>>> something from the atheros chip to output, but I was assuming I >>>> couldn't. The main reason I was looking at the ath10k driver was to >>>> get as close to when the packets are transmitted as possible, to leave >>>> as little room for error in the switching as possible. >>>> >>>> However, it's possible that I'm hoping for too much there. I'd be >>>> interested to hear your thoughts on it. If I can't pull it off, I'll >>>> move to an approach outside ath10k. >>> >>> >>> The driver just sends pkts to the firmware, it is the firmware that >>> knows when a pkt is to be transmitted, so I think you would have to have >>> some >>> hooks low in the firmware tx logic to do what you want. And you would >>> need some >>> hardware output from the NIC. >>> >>> I am guessing it would require quite a bit of changes to the firmware, >>> possibly very tricky/hacky ones, and hardware output on your NIC. >>> >>> Thanks, >>> Ben >>> >>> -- >>> Ben Greear >>> Candela Technologies Inc http://www.candelatech.com >>> >>> >>> _______________________________________________ >>> ath10k mailing list >>> ath10k@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/ath10k > -- Ben Greear Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k