From: Bob Copeland <me@bobcopeland.com>
To: ath10k@lists.infradead.org
Subject: Re: [PATCH RFC] out-of-order frames
Date: Wed, 20 Feb 2019 12:05:25 -0500 [thread overview]
Message-ID: <20190220170525.GA28857@localhost> (raw)
In-Reply-To: <20190219202554.GA5065@localhost>
On Tue, Feb 19, 2019 at 03:25:54PM -0500, Bob Copeland wrote:
> - This is on a 4.14.94 kernel:
>
> [ 12.454034] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
> [ 12.487148] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.4-00104 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast crc32 4317698a
Just a few follow-up observations:
- seems specific to mesh mode; in AP mode I see, e.g.:
[ 7762.442026] XXX start rx ba session peer 2
...where that is a printk I added before we setup the session in mac80211.
- newest firmware does not fix
- addba requests are robust management frames and I was initially testing
with pmf=1; however, I turned that off and it is still broken
--
Bob Copeland %% https://bobcopeland.com/
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2019-02-20 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 20:25 [PATCH RFC] out-of-order frames Bob Copeland
2019-02-20 17:05 ` Bob Copeland [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=20190220170525.GA28857@localhost \
--to=me@bobcopeland.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