From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 1/2] ap: Remove opt-out DisableHT for opt-in EnableHT
Date: Fri, 2 Jun 2023 07:58:11 -0700 [thread overview]
Message-ID: <20230602145812.22010-1-prestwoj@gmail.com> (raw)
HT support was added to AP mode which was not widely tested
across many different wireless adapters. The adapters tested
did not seem to mind the channel width setting but recently
several users have experienced AP mode breaking using the
default/no configuration. Disabling HT works around the issue
and allows AP mode to start in these cases.
This deserves further investigation but its looking like more
often than not users need to add DisableHT. This isn't so bad
for AP profiles since the user has to create a profile anyways,
but for the Start command its best if it "just works". To error
on the side of caution DisableHT is being renamed to EnableHT
making it opt-in rather than opt-out.
---
src/ap.c | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/src/ap.c b/src/ap.c
index 398e469a..7e6c868e 100644
--- a/src/ap.c
+++ b/src/ap.c
@@ -3668,19 +3668,22 @@ static int ap_load_config(struct ap_state *ap, const struct l_settings *config,
ap->band = BAND_FREQ_2_4_GHZ;
}
- if (l_settings_has_key(config, "General", "DisableHT")) {
+ if (l_settings_has_key(config, "General", "EnableHT")) {
bool boolval;
- if (!l_settings_get_bool(config, "General", "DisableHT",
+ if (!l_settings_get_bool(config, "General", "EnableHT",
&boolval)) {
- l_error("AP [General].DisableHT not a valid boolean");
+ l_error("AP [General].EnableHT not a valid boolean");
return -EINVAL;
}
- ap->supports_ht = !boolval;
- } else
- ap->supports_ht = wiphy_get_ht_capabilities(wiphy, ap->band,
- NULL) != NULL;
+ if (!wiphy_get_ht_capabilities(wiphy, ap->band, NULL)) {
+ l_error("AP hardware does not support HT");
+ return -EINVAL;
+ }
+
+ ap->supports_ht = boolval;
+ }
if (!ap_validate_band_channel(ap)) {
l_error("AP Band and Channel combination invalid");
--
2.25.1
next reply other threads:[~2023-06-02 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 14:58 James Prestwood [this message]
2023-06-02 14:58 ` [PATCH 2/2] doc: document EnableHT option James Prestwood
2023-06-06 15:40 ` [PATCH 1/2] ap: Remove opt-out DisableHT for opt-in EnableHT Denis Kenzior
2023-06-06 16:11 ` James Prestwood
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=20230602145812.22010-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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.