From: Oleksij Rempel <linux@rempel-privat.de>
To: Melroy van den Berg <webmaster1989@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] IBSS network crashes after one device leaves network
Date: Wed, 24 Dec 2014 17:46:18 +0100 [thread overview]
Message-ID: <549AEDDA.3050507@rempel-privat.de> (raw)
In-Reply-To: <loom.20141224T034313-122@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Am 24.12.2014 um 03:45 schrieb Melroy van den Berg:
> Oleksij Rempel <linux@...> writes:
>> hmm.. suddenly rate scaling is not singe limitation of ath9k-htc.
>> Firmware keeps some information for each STA and trying to reduce usb
>> bandwidth. If i understand it correctly, ath10k works in the same way.
>> It means, early or soon we need to work with some hard limits.
>
>
> I think it's exactly the same limit as for the AP mode.
>
> See: https://lists.ath9k.org/pipermail/ath9k-devel/2013-April/010513.html
>
> There should be some solution, atleast the IBSS network shouldn't crash.
Yes,
right now i have no time to work on this problem. To anyone who can, you
are really welcome.
Here is a script to crash at leas one pear from adhoc network:
http://pastebin.com/KhXgQ15V
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
prev parent reply other threads:[~2014-12-24 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C7367401563A9D46BC5A92B9456C061D48D210@G08CNEXMBPEKD03.g08.fujitsu.local>
2014-10-20 19:09 ` [ath9k-devel] IBSS network crashes after one device leaves network Oleksij Rempel
2014-10-20 19:29 ` Johannes Berg
2014-10-21 13:56 ` Oleksij Rempel
2014-12-24 2:45 ` Melroy van den Berg
2014-12-24 16:46 ` Oleksij Rempel [this message]
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=549AEDDA.3050507@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=linux-wireless@vger.kernel.org \
--cc=webmaster1989@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).