From: Ben Greear <greearb@candelatech.com>
To: Zach Sherin <zach@netblazr.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:02:34 -0700 [thread overview]
Message-ID: <5755BABA.1030006@candelatech.com> (raw)
In-Reply-To: <CAOiRWuUjugeDtRTQUWBzoCq58L8XfW7aYQTHa=Mnf4smx6AR2g@mail.gmail.com>
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
next prev parent reply other threads:[~2016-06-06 18:03 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 [this message]
[not found] ` <CAJ-VmomKzRAkJNQr2Sg=j57uPfptPiRs1Q026dPeuQv0jMx-Og@mail.gmail.com>
2016-06-06 18:48 ` Zach Sherin
2016-06-06 18:57 ` Ben Greear
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=5755BABA.1030006@candelatech.com \
--to=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox