From: Ben Greear <greearb@candelatech.com>
To: Alessandro Bolletta <alessandro@mediaspot.net>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: R: R: Link can't get estabilished over RB911AC boards
Date: Mon, 21 Sep 2015 16:34:46 -0700 [thread overview]
Message-ID: <56009416.5000003@candelatech.com> (raw)
In-Reply-To: <F52F175DFC537F48A43937B50B44BCA2820829AD@EXCHANGE.mediaspot.local>
On 09/21/2015 04:20 PM, Alessandro Bolletta wrote:
> Ok Ben, thanks for you infos.
>
> Just for curiosity: do you think that ath10k could be better in performances than official QCA reference drivers (the same used in proprietary distros as RouterOS, for example)?
As far as I know, the 'official' ath10k dev kits use the same firmware that is available
on the public git firmware tree, so probably firmware performance is similar unless some third-party company
has acquired firmware source code and put some considerable effort into it.
My CT firmware is primarily focused on stability and features. I have not made a lot
of effort to try to optimize speed, though I have had a few people tell me my firmware
was faster, and I don't recall anyone telling me it was slower. I suspect it is
basically about the same.
Possibly a very recent linux kernel + ath10k driver is more efficient than
reference driver OS's, but I am guessing that would depend greatly on how
the reference OS is tuned for the hardware in question.
I test on x86 primarily, and have plenty of CPU, so I haven't been
worrying too much about CPU resources on the host.
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:[~2015-09-21 23:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 19:57 Link can't get estabilished over RB911AC boards Alessandro Bolletta
2015-09-21 20:36 ` Ben Greear
2015-09-21 22:18 ` R: " Alessandro Bolletta
2015-09-21 23:18 ` Ben Greear
2015-09-21 23:20 ` R: " Alessandro Bolletta
2015-09-21 23:34 ` Ben Greear [this message]
2015-09-22 21:09 ` Alessandro Bolletta
2015-09-22 21:14 ` Ben Greear
[not found] ` <CAGNwC3nKb_tJnL44tu0jaV5h2hX2KLqoiLdm-GR+myyKRHZdBQ@mail.gmail.com>
2015-09-22 21:26 ` Alessandro Bolletta
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=56009416.5000003@candelatech.com \
--to=greearb@candelatech.com \
--cc=alessandro@mediaspot.net \
--cc=ath10k@lists.infradead.org \
/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.