From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>, Avery Pennarun <apenwarr@gmail.com>
Subject: Re: Unicast packets stop being transmitted to a particular station, under load, when WPA2 is enabled
Date: Thu, 16 Jun 2016 17:01:55 -0700 [thread overview]
Message-ID: <57633DF3.3070009@candelatech.com> (raw)
In-Reply-To: <877g57bl9a.fsf@kamboji.qca.qualcomm.com>
On 05/27/2014 02:53 AM, Kalle Valo wrote:
> Hi Avery,
>
> Avery Pennarun <apenwarr@gmail.com> writes:
>
>> On Sun, May 11, 2014 at 11:09 PM, Ben Greear <greearb@candelatech.com> wrote:
>>> Can you reproduce with any other type of station
>>> device?
>>
>> I'll try. It's a little tricky since it seems to involve running
>> Chrome, etc, rather than my usual command-line tests for which I have
>> a wider variety of clients.
>
> did you have a chance to check with other clients? It would be good to
> know if this is macbook specific interoparibility problem or something
> else.
>
So, to resurrect an ancient thread....
I have a user (who wants to buy and sell lots and lots of QCA chipset NICS!)
of my 10.1 firmware hitting this problem. They have a way to reproduce
it readily, though for one reason or another, I cannot reproduce it locally using what
should be an identical setup.
Their problem cannot be reproduced in a stock 10.2 firmware (firmware-3.bin, I think) on a newer kernel,
while that newer kernel does hit the problem with my 10.1 firmware. So, it is
definitely something in the firmware. Their system cannot use 10.2 firmware
at the moment because it is based on an older kernel.
So, I am curious if someone would like to give me a hint as to what was the actual
firmware fix for this issue. I don't need code snippets since that stuff is
private...but just a method name and/or file or something and I should be able
to track it down and backport just that fix. I've tried comparing obvious code
spots in 10.1 and 10.2 firmware, but nothing obvious jumps out.
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-17 0:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 1:57 Unicast packets stop being transmitted to a particular station, under load, when WPA2 is enabled Avery Pennarun
2014-05-12 2:07 ` Dave Taht
2014-05-12 2:29 ` Avery Pennarun
2014-05-12 2:42 ` Dave Taht
2014-05-12 2:46 ` Dave Taht
2014-05-12 14:49 ` Adrian Chadd
2014-05-12 3:09 ` Ben Greear
2014-05-12 3:54 ` Avery Pennarun
2014-05-12 4:05 ` Ben Greear
2014-05-12 4:56 ` Avery Pennarun
2014-05-12 5:05 ` Ben Greear
2014-05-12 5:19 ` Avery Pennarun
2014-05-12 7:07 ` Avery Pennarun
2014-05-12 8:21 ` Avery Pennarun
2014-05-12 14:10 ` Ben Greear
2014-05-14 19:07 ` Avery Pennarun
2014-05-14 19:26 ` Dave Taht
2014-05-14 19:38 ` Adrian Chadd
2014-05-15 6:12 ` Avery Pennarun
2014-05-16 20:01 ` Dave Taht
2014-05-16 20:10 ` Adrian Chadd
2014-05-19 21:04 ` Adrian Chadd
2014-05-19 21:07 ` Dave Taht
2014-05-19 21:09 ` Adrian Chadd
2014-05-14 20:20 ` Adrian Chadd
2014-05-14 20:46 ` Adrian Chadd
2014-05-14 21:45 ` Avery Pennarun
2014-05-27 9:53 ` Kalle Valo
2016-06-17 0:01 ` Ben Greear [this message]
2014-05-12 14:53 ` Adrian Chadd
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=57633DF3.3070009@candelatech.com \
--to=greearb@candelatech.com \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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.