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: Wed, 3 Aug 2016 11:51:09 +0900 [thread overview]
Message-ID: <bb69b031-53ad-4649-bd1d-e95ca7a0cc70@gmail.com> (raw)
In-Reply-To: <1470122837.2665.5.camel@sipsolutions.net>
On 2016年08月02日 16:27, Johannes Berg wrote:
> This explicitly configures *HT capability* though - that's even the
> name of the parameter. If you enable HT40 in the capability, the
> resulting BSS might still not actually *use* 40 MHz bandwidth, as
> required by overlapping BSS detection.
OK, I see.
HT Capabilities element = Defined by hardware and software spec of the
node. So it does not be modified after boot.
HT Operation element = Defined by surrounding environment and
configuration of the node. So it could be modified after boot.
So, if the node supports HT40, HT Capabilities shows HT40 is capable.
Now, I understand why you rejected this patch.
But now, when disable_ht=1, no HT Capabilities element in beacon even
though the node supports HT.
My trailing patch could solve the issue.
Masashi Honma.
next prev parent reply other threads:[~2016-08-03 2:51 UTC|newest]
Thread overview: 14+ 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-13 20:07 ` Yaniv Machani
2016-07-22 5:26 ` Masashi Honma
2016-07-22 5:26 ` Masashi Honma
2016-07-26 3:41 ` 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
2016-08-02 2:59 ` Masashi Honma
2016-08-02 7:27 ` Johannes Berg
2016-08-03 2:51 ` Masashi Honma [this message]
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=bb69b031-53ad-4649-bd1d-e95ca7a0cc70@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.