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.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
