On Fri, Mar 31, 2023 at 11:14:14AM +0200, Johannes Berg wrote: > On Thu, 2023-03-30 at 19:30 +0300, Jouni Malinen wrote: > Oh, no, I'm entirely happy with this happening in nl80211, it's just the > age-old question again of whether those upstream drivers will ever even > get support for it, or if we end up with more code that effectively > looks dead as far as upstream is concerned :-) > > If this actually came with a driver patch using it, the question > wouldn't even arise, since then it's clear why it's needed and what > for... This is one of those cases where the changes seem to be of general interest, but there is no immediate plans to work on any upstream driver to use that. As far as the current potentially applicable upstream drivers are concerned, I would not expect ath6kl to be extended to use this. I do not really know whether anyone maintaining the drivers for other vendors would be interested. This is a balance on what would be the cleanest design (i.e., the most appropriate nl80211 command for this type of configuration) and potential help for others vs. what could be done with a somewhat ugly vendor specific command before the start AP command. Since this specific case can be handled with a vendor command, I'm not planning on pushing strongly for this to get accepted into upstream nl80211, but it did seem to make sense to propose this to see if there would be sufficient interest for other drivers. -- Jouni Malinen PGP id EFC895FA
