From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: <linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>
Subject: Re: [PATCH 3/3] ath10k: implement mesh support
Date: Wed, 9 Sep 2015 12:10:38 +0300 [thread overview]
Message-ID: <87fv2o9cvl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87oahc9g9h.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Wed, 09 Sep 2015 10:57:30 +0300")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Bob Copeland <me@bobcopeland.com> writes:
>
>> Add support for mesh to ath10k. We simply use an AP virtual interface
>> in the firmware in order to enable beaconing without TSF adoption, and
>> use the raw (802.11) transmit mode.
>>
>> Due to firmware limitations, the firmware must operate in raw
>> (non-native 802.11) mode. As this is configured at firmware init time,
>> a new "rawmode" modparam is added, and mesh interfaces are available
>> only if rawmode=true. The firmware must advertise support for rawmode
>> (tested successfully with firmware 10.2.4.70-2).
>>
>> When loaded with rawmode=1, ath10k can operate an open mesh STA via
>> something like the following:
>>
>> ip link set wlan0 down
>> iw dev wlan0 set type mp
>> ip link set wlan0 up
>> iw dev wlan0 set freq 5745 80 5775
>> iw dev wlan0 mesh join mesh-vht
>>
>> Signed-off-by: Bob Copeland <me@bobcopeland.com>
>
> I did a quick smoke test and saw the splat below. It's this warning from
> cfg80211:
>
> /*
> * Don't advertise an unsupported type
> * in a combination.
> */
> if (WARN_ON((wiphy->interface_modes & types) != types))
> return -EINVAL;
Forgot to mention that this was with 10.2.4.70.6-2 (which has the raw
feature bit set, will push it soon) but rawmode modparam not set. And I
had applied your patches on top of ath.git master branch (commit
d89281c7d6bb9).
--
Kalle Valo
next prev parent reply other threads:[~2015-09-09 9:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 10:57 [PATCH 0/3] mesh support for ath10k Bob Copeland
2015-08-27 10:57 ` [PATCH 1/3] ath10k: enable monitor when OTHER_BSS requested Bob Copeland
2015-08-27 10:57 ` [PATCH 2/3] ath10k: check for encryption before adding MIC_LEN Bob Copeland
2015-08-27 10:57 ` [PATCH 3/3] ath10k: implement mesh support Bob Copeland
2015-08-29 17:11 ` Jason Andryuk
2015-08-29 22:25 ` Bob Copeland
2015-08-30 17:43 ` Yeoh Chun-Yeow
2015-09-16 12:39 ` Bob Copeland
2015-09-17 17:48 ` Yeoh Chun-Yeow
2015-09-17 23:56 ` Peter Oh
2015-09-01 3:02 ` Jason Andryuk
2015-09-09 7:57 ` Kalle Valo
2015-09-09 9:10 ` Kalle Valo [this message]
2015-09-09 16:49 ` Bob Copeland
2015-09-10 5:46 ` Kalle Valo
2015-09-10 7:22 ` Johannes Berg
2015-09-15 7:21 ` Peter Oh
2015-09-16 12:32 ` Bob Copeland
2015-09-09 11:08 ` Bob Copeland
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=87fv2o9cvl.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).