From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Re: Getting a 'no-ack' tx status?
Date: Sat, 28 Feb 2015 09:52:48 -0800 [thread overview]
Message-ID: <54F20070.6070905@candelatech.com> (raw)
In-Reply-To: <54F0FD17.2080603@candelatech.com>
I think I managed to hack the CT firmware to return the
tx-completion status (OK, XRETRY, DROP) when it is returning the
tx-rate info, and patched the driver to pay attention to it...
A brief test showed some failed-retry counters reported by
the mac80211 stack, so that looks promising.
Will do some more testing when I get a chance.
Thanks,
Ben
On 02/27/2015 03:26 PM, Ben Greear wrote:
> Someone reported to me that they never see the
> tx_done->no_ack flag set on their AP, even when stations are falling
> off the network due to not receiving ACKs.
>
> if (tx_done->no_ack)
> info->flags &= ~IEEE80211_TX_STAT_ACK;
>
>
> I am having no luck finding the corresponding code in the 10.1.467
> firmware that would cause this to work, but maybe I am just not looking
> in the right place.
>
> Has anyone done any testing to see if ath10k actually reports ACK failures
> properly back up the stack?
>
> 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-02-28 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 23:26 Getting a 'no-ack' tx status? Ben Greear
2015-02-28 17:52 ` Ben Greear [this message]
2015-03-02 8:45 ` Michal Kazior
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=54F20070.6070905@candelatech.com \
--to=greearb@candelatech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox