From: Bob Copeland <me@bobcopeland.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org
Subject: Re: [PATCH 0/3] ath10k mesh support
Date: Tue, 18 Aug 2015 08:42:33 -0400 [thread overview]
Message-ID: <20150818124233.GA867@localhost> (raw)
In-Reply-To: <878u98dddv.fsf@kamboji.qca.qualcomm.com>
On Tue, Aug 18, 2015 at 02:50:20PM +0300, Kalle Valo wrote:
> Bob Copeland <me@bobcopeland.com> writes:
> >
> > if=wlan0
> > meship=10.10.1.10
> > ip link set $if down
> > ip addr flush $if
> > iw dev $if set type mp
> > ip link set $if up
> > ip addr add $meship/24 dev $if
> > iw dev $if set freq 5745 80 5775
> > iw dev $if mesh join mesh-vht
>
> Can you add this example to patch 3, please? Also mention in patch 3
> what firmware version you used to test this. Oh, but I haven't made a
> firmware release with RAW_MODE flag set. Need to do that.
Sure -- yes I guess this patch is also missing a check for the firmware
feature flag (although it works on 10.2.4.70-2 apparently) -- will add
once you do such a release.
> > * I'm not crazy about requiring a modparam and advertising mesh interfaces
> > that are only really usable when the modparam is set, but I'm not sure how
> > to set rx decap mode on the fly and whether we can do that on a per-vif
> > basis.
>
> This is good enough for now, but I would prefer that we advertise mesh
> support to user space only when the rawmode modparam is set. I guess we
> should start building all iface_limits dynamically? But that's future
> cleanup.
I started down this path originally, but "it's complicated." There's a
bit of a combinatorial explosion problem since there are already 4
different if_limits with different combinations. I guess we could
iterate over them and set the bits just before calling into mac80211,
but we'd need to cast away a const or two.
--
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-18 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 15:25 [PATCH 0/3] ath10k mesh support Bob Copeland
2015-08-16 15:25 ` [PATCH 1/3] ath10k: enable monitor when OTHER_BSS requested Bob Copeland
2015-08-16 15:25 ` [PATCH 2/3] ath10k: check for encryption before adding MIC_LEN Bob Copeland
2015-08-16 15:25 ` [PATCH 3/3] ath10k: implement mesh support Bob Copeland
2015-08-17 11:06 ` Unable to set channel above 100 with latest CT Kernel and Firmware Harms, Hannes
2015-08-18 11:54 ` Kalle Valo
2015-08-18 14:52 ` Ben Greear
2015-08-18 11:50 ` [PATCH 0/3] ath10k mesh support Kalle Valo
2015-08-18 12:42 ` Bob Copeland [this message]
2015-08-18 16:04 ` 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=20150818124233.GA867@localhost \
--to=me@bobcopeland.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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