From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: Updated CT firmware uploaded.
Date: Thu, 09 Jul 2015 10:55:38 -0700 [thread overview]
Message-ID: <559EB59A.2000509@candelatech.com> (raw)
Changes since last email of this nature:
* Fix crash related to a race where packet was (re)sent to a peer
that had been deleted. The crash was in the rate-ctrl logic,
and was seen when an Apple MAC laptop with bcom AC NIC did a network
discovery while connected to ath10k AP and while running iperf.
The ath10k AP disconnects the MAC in this case, which can trigger
the firmware bug. Possibly, a better solution is to force a flush
of the peer's tx queue when deleting a peer. A note has been made
to revisit this in the future.
* Allow over-riding thresh62_ext and some ack-timing registers.
thresh62_ext has been tested, the others have not at this time.
This may help with some regulatory testing issues.
* Fix beacon concurrency issues: The firmware did not properly go
in an 'rx-all-beacons' mode when more than 2 station vdevs were
created. This left the third receiving no beacons if connected to
a different AP from the others.
And note: For anyone doing IBSS/ADHOC with my firmware, please use
the beta builds until I can do an official version-14 release.
http://www.candelatech.com/ath10k.php
http://www.candelatech.com/downloads/ath10k-fw-beta/
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 reply other threads:[~2015-07-09 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 17:55 Ben Greear [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-15 21:30 Updated CT firmware uploaded Ben Greear
2015-06-12 16:54 Ben Greear
2015-05-29 16:47 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=559EB59A.2000509@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 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.