aboutsummaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
authorSreeramya Soratkal <ssramya@codeaurora.org>2020-11-18 10:51:29 (GMT)
committerJouni Malinen <j@w1.fi>2020-11-23 18:45:31 (GMT)
commited24bad1d98d50f94e024f71093cdbd76cc0d872 (patch)
tree1e00f581e54b25658315ff7d667bf1e81f025f06 /tests
parent5b782ff620002c21f193034ab911e6524b31785a (diff)
downloadhostap-ed24bad1d98d50f94e024f71093cdbd76cc0d872.zip
hostap-ed24bad1d98d50f94e024f71093cdbd76cc0d872.tar.gz
hostap-ed24bad1d98d50f94e024f71093cdbd76cc0d872.tar.bz2
AP: Check driver support while auto-selecting bandwidth for AP/P2P GO
If the maximum operating channel width for AP/P2P GO is not specified, it is auto-selected during configuration. While selecting the channel width, if VHT is supported and 160 MHz channels are available, 160 MHz channel width is preferred to 80 MHz. During the selection of the channel width, the corresponding driver capabilities were not checked. As a result, the AP/P2P GO configuration was set to use the available 160 MHz channels even if the driver did not have capability to support the 160 MHz channel width causing failure to start the AP/P2P GO. Fix this by checking the driver support for the 160 MHz channel width while selecting the channel width for AP/P2P GO. Signed-off-by: Sreeramya Soratkal <ssramya@codeaurora.org>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions