We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, with kernel 4.19, it's not possible to set wl18xx devices in AP + Mesh mode. To accomplish that the following patch must be applied:
diff --git a/drivers/net/wireless/ti/wl18xx/main.c b/drivers/net/wireless/ti/wl18xx/main.c index 496b9b63cea1..db5bc51ce51c 100644 --- a/drivers/net/wireless/ti/wl18xx/main.c +++ b/drivers/net/wireless/ti/wl18xx/main.c @@ -1905,12 +1905,14 @@ wl18xx_iface_combinations[] = { .max_interfaces = 3, .limits = wl18xx_iface_limits, .n_limits = ARRAY_SIZE(wl18xx_iface_limits), + .beacon_int_min_gcd = 1, .num_different_channels = 2, }, { .max_interfaces = 2, .limits = wl18xx_iface_ap_limits, .n_limits = ARRAY_SIZE(wl18xx_iface_ap_limits), + .beacon_int_min_gcd = 1, .num_different_channels = 1, .radar_detect_widths = BIT(NL80211_CHAN_NO_HT) | BIT(NL80211_CHAN_HT20) |
See the following post in TI's Wi-Fi Forum for extra details:
WL1835MOD: Unable to activate simultaneous AP and mesh roles
The text was updated successfully, but these errors were encountered:
@JoseGoncalves thanks
@RobertCNelson include this in the next release?
Sorry, something went wrong.
This and other mesh related patches are now available in TI's Git repository:
https://git.ti.com/cgit/wilink8-wlan/build-utilites/tree/patches/kernel_patches/4.19.38?h=r8.8
pdp7
No branches or pull requests
Currently, with kernel 4.19, it's not possible to set wl18xx devices in AP + Mesh mode.
To accomplish that the following patch must be applied:
See the following post in TI's Wi-Fi Forum for extra details:
WL1835MOD: Unable to activate simultaneous AP and mesh roles
The text was updated successfully, but these errors were encountered: