All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Zach Sherin <zach@netblazr.com>, Adrian Chadd <adrian.chadd@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Any tips on where per-packet antenna selection could be pushed?
Date: Mon, 6 Jun 2016 11:57:51 -0700	[thread overview]
Message-ID: <5755C7AF.6020203@candelatech.com> (raw)
In-Reply-To: <CAOiRWuUL9RC61pdieiEh3ZtWFGLomHzPxqbbVE3Oe_3043Zv2g@mail.gmail.com>

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 <adrian.chadd@gmail.com> 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" <greearb@candelatech.com> 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 <greearb@candelatech.com>
>>> Candela Technologies Inc  http://www.candelatech.com
>>>
>>>
>>> _______________________________________________
>>> ath10k mailing list
>>> ath10k@lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/ath10k
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2016-06-06 18:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 17:12 Any tips on where per-packet antenna selection could be pushed? Zach Sherin
2016-06-06 17:21 ` Ben Greear
2016-06-06 17:24   ` Zach Sherin
2016-06-06 17:28     ` Ben Greear
2016-06-06 17:59       ` Zach Sherin
2016-06-06 18:02         ` Ben Greear
     [not found]           ` <CAJ-VmomKzRAkJNQr2Sg=j57uPfptPiRs1Q026dPeuQv0jMx-Og@mail.gmail.com>
2016-06-06 18:48             ` Zach Sherin
2016-06-06 18:57               ` Ben Greear [this message]
2016-06-06 19:22                 ` Zach Sherin
2016-06-07  6:24                   ` Janusz Dziedzic
2016-06-07  7:40                     ` Adrian Chadd
2016-06-07  7:53                       ` Michal Kazior
2016-06-07 16:30                         ` Adrian Chadd
2016-06-08 13:53                           ` Michal Kazior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5755C7AF.6020203@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian.chadd@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=zach@netblazr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.