From: Ben Greear <greearb@candelatech.com>
To: Pushpal Sidhu <psidhu@gateworks.com>
Cc: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: IBSS mode is now supported by CT firmware.
Date: Mon, 01 Dec 2014 09:57:50 -0800 [thread overview]
Message-ID: <547CAC1E.2000709@candelatech.com> (raw)
In-Reply-To: <CAD1M060=TLNR-ZFdTiwq8tAbC=2h2zsKbxyFkkL1N5pvfwLWEA@mail.gmail.com>
On 12/01/2014 09:38 AM, Pushpal Sidhu wrote:
> On Fri, Nov 28, 2014 at 8:28 AM, Ben Greear <greearb@candelatech.com> wrote:
>> Do you have any reason to believe the problem is in the driver or mac80211
>> stack, or is this all a firmware issue?
> Because the rate control logic is embedded in the firmware (I believe
> this is the reason why we don't have a nice 'rc_stats' table) seems to
> point to a firmware issue.
>
>> And, if anyone has a different /AC NIC that can do IBSS, I'm curious
>> if ath10k will receive at higher speeds?
> So I just created an adhoc network with an ath9k radio (HT40+) with an
> ath10k radio (with HT40+) and found that the ath9k stayed at HT40/SGI
> MCS7. Checking on the ath10k, I found the same rate (150mbps) was
> being used.
>
> A very interesting note, however, is that realistic transfer rates are
> 27mbps TCP, 37mbps UDP from ath9k->ath10k. ath10k->ath9k has realistic
> transfer rates of 4.17mbps TCP, 5.18mbps UDP and rates go back to the
> 6mbps we see earlier.
It may be a bit before I can get back to working on this effort,
but I am reading the email and it will help me when I do have time
to work on this again.
If you have time, can you see if you can get encryption working with
ath9k to ath9k? I could not get that working, and I am not sure if
it is my supplicant setup or if I have some other bugs somewhere...
Please post config files if you do get it working.
And, what is ath9k to ath9k transfer rates?
Thanks,
Ben
>
> - Pushpal
>
--
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:[~2014-12-01 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 0:59 IBSS mode is now supported by CT firmware Ben Greear
2014-11-26 1:21 ` Yeoh Chun-Yeow
2014-11-26 1:39 ` Ben Greear
2014-11-26 1:48 ` Yeoh Chun-Yeow
2014-11-26 1:50 ` Ben Greear
2014-11-26 2:14 ` Yeoh Chun-Yeow
2014-11-26 1:57 ` Dave Taht
2014-11-26 22:36 ` Pushpal Sidhu
2014-11-27 1:04 ` Yeoh Chun-Yeow
2014-11-28 11:42 ` Yeoh Chun-Yeow
2014-11-28 16:28 ` Ben Greear
2014-11-29 0:25 ` Yeoh Chun-Yeow
2014-12-01 17:38 ` Pushpal Sidhu
2014-12-01 17:57 ` Ben Greear [this message]
2014-12-04 15:28 ` Sven Eckelmann
2014-12-01 17:13 ` Pushpal Sidhu
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=547CAC1E.2000709@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=psidhu@gateworks.com \
--cc=yeohchunyeow@gmail.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.