From: Felix Fietkau <nbd@openwrt.org>
To: Alexander Simon <alexander.simon@saxnet.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC v3 2/3] nl80211: channel type attribute for IBSS
Date: Fri, 24 Jun 2011 20:56:32 +0200 [thread overview]
Message-ID: <4E04DDE0.2020008@openwrt.org> (raw)
In-Reply-To: <1308671544.2656.8.camel@alex-2>
On 2011-06-21 5:52 PM, Alexander Simon wrote:
> Allow nl80211 to set a ht channel for ibss.
>
> Signed-off-by: Alexander Simon<alexander.simon@saxnet.de>
>
> diff -Nrup a/net/wireless/nl80211.c b/net/wireless/nl80211.c
> --- a/net/wireless/nl80211.c 2011-06-01 21:04:33.000000000 +0200
> +++ b/net/wireless/nl80211.c 2011-06-21 13:21:38.000000000 +0200
> @@ -4266,12 +4266,37 @@ static int nl80211_join_ibss(struct sk_b
> ibss.ie_len = nla_len(info->attrs[NL80211_ATTR_IE]);
> }
>
> - ibss.channel = ieee80211_get_channel(wiphy,
> - nla_get_u32(info->attrs[NL80211_ATTR_WIPHY_FREQ]));
> - if (!ibss.channel ||
> + if (info->attrs[NL80211_ATTR_WIPHY_CHANNEL_TYPE]) {
> + enum nl80211_channel_type channel_type;
> +
> + channel_type = nla_get_u32(
> + info->attrs[NL80211_ATTR_WIPHY_CHANNEL_TYPE]);
> + if (channel_type != NL80211_CHAN_NO_HT&&
> + channel_type != NL80211_CHAN_HT20&&
> + channel_type != NL80211_CHAN_HT40PLUS&&
> + channel_type != NL80211_CHAN_HT40MINUS)
> + return -EINVAL;
> + ibss.channel_type = channel_type;
> + } else {
> + ibss.channel_type = NL80211_CHAN_NO_HT;
> + }
> +
> + ibss.channel = rdev_freq_to_chan(rdev,
> + nla_get_u32(info->attrs[NL80211_ATTR_WIPHY_FREQ]),
> + ibss.channel_type);
> + /*if (!ibss.channel ||
> + ibss.channel->flags& IEEE80211_CHAN_PASSIVE_SCAN ||
> ibss.channel->flags& IEEE80211_CHAN_NO_IBSS ||
> - ibss.channel->flags& IEEE80211_CHAN_DISABLED)
> + ibss.channel->flags& IEEE80211_CHAN_RADAR)
> + return -EINVAL;
> + if ((ibss.channel_type == NL80211_CHAN_HT40PLUS ||
> + ibss.channel_type == NL80211_CHAN_HT40MINUS)&&
> + !can_beacon_sec_chan(&rdev->wiphy, ibss.chan, ibss.channel_type)) {
> + printk(KERN_DEBUG
> + "cfg80211: Secondary channel not "
> + "allowed to initiate communication\n");
> return -EINVAL;
> + }*/
That last part looks like a debugging hack, you should remove it before
re-submitting that patch.
- Felix
next prev parent reply other threads:[~2011-06-24 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 15:45 [RFC v3 1/3] mac80211: add some helper functions Alexander Simon
2011-06-21 15:52 ` [RFC v3 2/3] nl80211: channel type attribute for IBSS Alexander Simon
2011-06-24 18:56 ` Felix Fietkau [this message]
2011-07-04 10:07 ` Alexander Simon
2011-07-04 10:10 ` Johannes Berg
2011-06-27 12:46 ` Johannes Berg
2011-06-21 15:53 ` [RFC v3 3/3] mac80211: HT operation in IBSS Alexander Simon
2011-06-24 19:21 ` Felix Fietkau
2011-06-27 12:50 ` Johannes Berg
2011-06-27 12:51 ` Johannes Berg
2011-06-21 16:01 ` patch for iw Alexander Simon
2011-06-27 12:42 ` Johannes Berg
2011-06-21 16:02 ` [RFC v3 1/3] mac80211: add some helper functions Johannes Berg
2011-06-24 19:01 ` Felix Fietkau
2011-06-27 12:46 ` Johannes Berg
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=4E04DDE0.2020008@openwrt.org \
--to=nbd@openwrt.org \
--cc=alexander.simon@saxnet.de \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).