From: Bob Copeland <me@bobcopeland.com>
To: ath10k@lists.infradead.org
Subject: Re: attempting mesh on ath10k
Date: Sun, 12 Jul 2015 21:43:33 -0400 [thread overview]
Message-ID: <20150713014333.GA14152@localhost> (raw)
In-Reply-To: <20150712142532.GA24495@localhost>
[trimmed CC to list]
On Sun, Jul 12, 2015 at 10:25:32AM -0400, Bob Copeland wrote:
> It looks like unicast self-protected action frames (peering) works fine, but
> broadcast multihop action frames (PREQs) never go over the air. Does
> this sound familiar to anyone?
Actually, it's any group addressed frame. I tried playing with various
values for htt_data_tx_ext_tid as well as just using the tid on the frame
(in mesh group addressed frames still have a qos header with tid=0).
[ 662.170000] XXX htt tx completion msdu_id 0 discard 0 no_ack 0 success 1
[ 662.470000] XXX tx seq: 264 txmode 0
[ 662.470000] XXX htt tx flags0 5 flags1 3136 len 39 id 0 frags_paddr 07337028, msdu_paddr 06513e2e vdev 0 tid 17 freq 0
[ 662.480000] XXX htt tx completion msdu_id 0 discard 0 no_ack 0 success 1
[ 662.600000] XXX tx seq: 265 txmode 0
[ 662.600000] XXX htt tx flags0 5 flags1 2048 len 156 id 0 frags_paddr 07337028, msdu_paddr 06932028 vdev 0 tid 0 freq 0
[ 662.620000] XXX tx seq: 266 txmode 0
[ 662.620000] XXX htt tx flags0 5 flags1 2048 len 116 id 1 frags_paddr 07337000, msdu_paddr 06921028 vdev 0 tid 0 freq 0
[ 662.630000] XXX htt tx completion msdu_id 0 discard 0 no_ack 1 success 0
[ 662.640000] XXX htt tx completion msdu_id 1 discard 0 no_ack 1 success 0
[ 663.090000] XXX tx seq: 267 txmode 0
The 'success 1' ones are unicast, the success 0 are mcast (in this case
using the frame's tid, otherwise it would be 16.)
Kind of odd that it's not working, since my earlier snapshot worked...
I guess at worst I can bisect compat-wireless versions but that will
take some time.
--
Bob Copeland %% http://bobcopeland.com/
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-07-13 1:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 21:25 attempting mesh on ath10k Freddy Lee
2015-07-06 21:49 ` Bob Copeland
2015-07-06 21:54 ` Bob Copeland
2015-07-12 14:25 ` Bob Copeland
2015-07-13 1:43 ` Bob Copeland [this message]
2015-07-13 8:13 ` Michal Kazior
2015-07-13 10:57 ` Bob Copeland
2015-07-20 13:57 ` Bob Copeland
2015-08-13 3:14 ` Bob Copeland
-- strict thread matches above, loose matches on Subject: below --
2015-04-24 12:50 Bob Copeland
2015-04-24 17:55 ` Yeoh Chun-Yeow
2015-04-25 1:38 ` Ben Greear
2015-04-26 14:15 ` Bob Copeland
2015-04-26 15:42 ` Ben Greear
2015-04-27 13:00 ` Bob Copeland
2015-04-28 5:47 ` Michal Kazior
2015-04-28 12:25 ` Bob Copeland
2015-05-27 6:51 ` Bartosz Markowski
2015-05-27 11:12 ` Bob Copeland
2015-05-27 11:15 ` Bartosz Markowski
2015-04-28 12:41 ` Bob Copeland
2015-04-28 12:50 ` Yeoh Chun-Yeow
2015-04-28 12:57 ` Bob Copeland
2015-04-28 14: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=20150713014333.GA14152@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