From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
Cc: linux-wireless@vger.kernel.org,
Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCHv2 4/6] mac80211: add support for CSA in IBSS mode
Date: Fri, 16 Aug 2013 12:33:08 +0200 [thread overview]
Message-ID: <1376649188.15299.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1376058920-17779-5-git-send-email-siwu@hrz.tu-chemnitz.de>
On Fri, 2013-08-09 at 16:35 +0200, Simon Wunderlich wrote:
> Ths
This ;-)
> + case NL80211_IFTYPE_ADHOC:
> + if (!sdata->vif.bss_conf.ibss_joined)
> + return -EINVAL;
> +
> + if (params->chandef.width != sdata->u.ibss.chandef.width)
> + return -EINVAL;
> +
> + switch (params->chandef.width) {
> + case NL80211_CHAN_WIDTH_40:
> + if (cfg80211_get_chandef_type(¶ms->chandef) !=
> + cfg80211_get_chandef_type(&sdata->u.ibss.chandef))
> + return -EINVAL;
Is that really correct? It seems that you should be able to switch from
HT40- to HT40+ and vice versa when switching the channel?
And why disallow switching bandwidth (was above this code)? That doesn't
seem right either?
> +/* must hold sdata lock */
pretty useless comment if you have the assert in the function :)
> + rcu_read_lock();
> + ies = rcu_dereference(cbss->ies);
> + tsf = ies->tsf;
> + rcu_read_unlock();
> + cfg80211_put_bss(sdata->local->hw.wiphy, cbss);
> +
> + old_presp = rcu_dereference_protected(ifibss->presp,
> + lockdep_is_held(&sdata->wdev.mtx));
> +
> + presp = ieee80211_ibss_build_presp(sdata,
> + sdata->vif.bss_conf.beacon_int,
> + sdata->vif.bss_conf.basic_rates,
> + capability, tsf, &ifibss->chandef,
> + NULL, csa_settings);
This is pretty odd - why does the TSF have to go here? It needs to be
set by the device when transmitting anyway, no?
> +static void ieee80211_ibss_disconnect(struct ieee80211_sub_if_data *sdata)
> +{
Is this some refactoring that should be separate? I don't see how it's
really related to CSA? Maybe I'm missing something?
johannes
next prev parent reply other threads:[~2013-08-16 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 14:35 [PATCHv2 0/6] add IBSS channel switch announcement support Simon Wunderlich
2013-08-09 14:35 ` [PATCHv2 1/6] cfg80211: export cfg80211_chandef_dfs_required Simon Wunderlich
2013-08-09 14:35 ` [PATCHv2 2/6] mac80211: split off channel switch parsing function Simon Wunderlich
2013-08-16 10:25 ` Johannes Berg
2013-08-09 14:35 ` [PATCHv2 3/6] mac80211: move ibss presp generation in own function Simon Wunderlich
2013-08-16 10:26 ` Johannes Berg
2013-08-09 14:35 ` [PATCHv2 4/6] mac80211: add support for CSA in IBSS mode Simon Wunderlich
2013-08-16 10:33 ` Johannes Berg [this message]
2013-08-16 13:36 ` Simon Wunderlich
2013-08-19 10:35 ` Johannes Berg
2013-08-09 14:35 ` [PATCHv2 5/6] mac80211: send a CSA action frame when changing channel Simon Wunderlich
2013-08-09 14:35 ` [PATCHv2 6/6] nl80211: enable IBSS support for channel switch announcements Simon Wunderlich
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=1376649188.15299.11.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
/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).