From: Masashi Honma <masashi.honma@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Yaniv Machani <yanivma@ti.com>,
linux-kernel@vger.kernel.org, Meirav Kama <meiravk@ti.com>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template
Date: Tue, 2 Aug 2016 11:59:04 +0900 [thread overview]
Message-ID: <1c2d3cfc-b7fd-c8fd-4f74-14dd3aa3076e@gmail.com> (raw)
In-Reply-To: <75fef3ce-41a6-5845-e9be-d7ff052a07da@gmail.com>
> On 2016年08月01日 19:03, Johannes Berg wrote:
>>
>> But why is that behaviour *correct*? We still support 40 MHz bandwidth
>> things, we just don't use them if we disable HT40.
Or do you mean difference between "hardware capability" and "software
capability" ?
Do you think IEEE80211_HT_CAP_SUP_WIDTH_20_40 bit should be 1 if the
hardware capable of HT40 even though HT40 is disabled by
wpa_supplicant/hostapd ?
I have tested with hostapd. I compared these 2 configfiles.
hostapd0.conf
ht_capab=[HT40-]
hostapd1.conf
#ht_capab=[HT40-]
The IEEE80211_HT_CAP_SUP_WIDTH_20_40 bit in beacon was below.
hostapd0.conf
IEEE80211_HT_CAP_SUP_WIDTH_20_40 = 1
hostapd1.conf
IEEE80211_HT_CAP_SUP_WIDTH_20_40 = 0
So I think the bit should be zero if disabled also for mesh peer.
Masashi Honma.
next prev parent reply other threads:[~2016-08-02 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 20:07 [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template Yaniv Machani
2016-07-22 5:26 ` Masashi Honma
2016-07-26 3:41 ` Masashi Honma
2016-08-01 10:03 ` Johannes Berg
2016-08-01 12:30 ` Masashi Honma
2016-08-02 2:59 ` Masashi Honma [this message]
2016-08-02 7:27 ` Johannes Berg
2016-08-03 2:51 ` Masashi Honma
2016-08-03 6:50 ` Johannes Berg
2016-08-03 2:54 ` [PATCH] mac80211: Include HT Capabilities element if capable Masashi Honma
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=1c2d3cfc-b7fd-c8fd-4f74-14dd3aa3076e@gmail.com \
--to=masashi.honma@gmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meiravk@ti.com \
--cc=netdev@vger.kernel.org \
--cc=yanivma@ti.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).