On Thu, Feb 14, 2019 at 09:20:53PM -0800, Justin Capella wrote: > Having looked at the code a little bit today, this commit does however > prevent using the value of 0 which cfg80211 uses to indicate driver > default, could the condition perhaps be changed to == -1 like other > options? (With some type changing?) Which version of cfg80211 are you looking at? The current (and if I remember correctly this has not changed recently, if ever) version of cfg80211 enforce that NL80211_ATTR_BEACON_INTERVAL is present in nl80211_start_ap(). The value of that attribute is then verified in cfg80211_validate_beacon_int() and anything below 10, i.e., including 0, is rejected with -EINVAL. There is no concept of a "driver default" for beacon interval in cfg80211. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
