From: Bob Copeland <me@bobcopeland.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: attempting mesh on ath10k
Date: Wed, 12 Aug 2015 23:14:44 -0400 [thread overview]
Message-ID: <20150813031444.GA18358@localhost> (raw)
In-Reply-To: <CA+BoTQnSJWGq-Pq2aRLvOC9_ieR5GyYk=BoZsNLsszfYPZ-6+Q@mail.gmail.com>
On Mon, Jul 13, 2015 at 10:13:59AM +0200, Michal Kazior wrote:
> On 13 July 2015 at 03:43, Bob Copeland <me@bobcopeland.com> wrote:
> > [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).
>
> Just a quick question: did you try applying the sw crypto/raw mode
> patch[1] and using it for mesh?
>
> [1]: https://patchwork.kernel.org/patch/6600721/
Ok, I have this working again against the latest driver, including that
patch -- I don't think anything was wrong with it, just didn't have both
raw tx and decap set properly and had some baggage from the original
patch to jettison.
Still a bit WIP but this patchset against openwrt r46584 seems to work
for me:
http://bobcopeland.com/kernel/wl/20150812/
The mac80211 bits (except for VHT) are upstream but openwrt doesn't have
them yet.
(BTW thanks to Cococorp for sending me a few APs to make testing a lot easier!)
--
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-08-13 3:15 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
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 [this message]
-- 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=20150813031444.GA18358@localhost \
--to=me@bobcopeland.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
/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