From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Question on beacon-miss offloading.
Date: Thu, 11 Jun 2015 14:07:11 -0700 [thread overview]
Message-ID: <5579F87F.4070601@candelatech.com> (raw)
In my ath10k CT firmware, I am disabling the beacon-miss offloading
to save space and because it will not work with lots of virtual
stations.
But, it must be that I need some way to tell the stack that this
feature is not enabled, because when suddenly kill my AP, then
the ath10k station connected to it shows endless 'beacon loss' events
in 'iw events' output, but it never actually loses connection.
Stock firmware works fine, so probably I just need to disable
some feature flag when registering the ath10k hardware
when using CT firmware.
With stock firmware, I see a quick dissassociation due to inactivity.
I am having poor luck finding how a driver tells the stack
it has beacon miss offload or not, so, does anyone know how
this is controlled?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-06-11 21:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 21:07 Ben Greear [this message]
2015-06-11 23:38 ` Question on beacon-miss offloading Ben Greear
2015-06-12 6:03 ` Michal Kazior
2015-06-12 13:29 ` Ben Greear
2015-06-12 14:10 ` Krishna Chaitanya
2015-06-12 15:22 ` Ben Greear
2015-06-12 15:37 ` Ben Greear
2015-06-15 5:36 ` Michal Kazior
2015-06-15 15:35 ` Ben Greear
2015-06-15 19:45 ` Ben Greear
2015-06-16 5:29 ` Michal Kazior
2015-06-16 21:55 ` Ben Greear
2015-06-16 23:06 ` Ben Greear
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=5579F87F.4070601@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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 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).