On 6 June 2016 at 23:24, Janusz Dziedzic <[email protected]> wrote: > On 6 June 2016 at 21:22, Zach Sherin <[email protected]> wrote: >> That's what I thought. Thanks for confirming, and thanks again for >> your time and help! >> > BTW, check google: ath10k smart antenna > Seems 10.2 support this.
ooo cool. wonder how much of the useful bits it implements! -adrian > > BR > Janusz > >> Have a good one, >> Zach >> >> On Mon, Jun 6, 2016 at 2:57 PM, Ben Greear <[email protected]> wrote: >>> 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 <[email protected]> >>>> 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" <[email protected]> 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 <[email protected]> >>>>>> Candela Technologies Inc http://www.candelatech.com >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> ath10k mailing list >>>>>> [email protected] >>>>>> http://lists.infradead.org/mailman/listinfo/ath10k >>>> >>>> >>> >>> >>> -- >>> Ben Greear <[email protected]> >>> Candela Technologies Inc http://www.candelatech.com >>> >> >> _______________________________________________ >> ath10k mailing list >> [email protected] >> http://lists.infradead.org/mailman/listinfo/ath10k _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
