> > > Is there a problem with the "supported commands" list? > > My understanding is that in general the "supported commands" list is not > well-maintained. Not every nl80211 command is represented in the list so > user-space can not know whether it is missing or not supported. > For this particular START_SCHED_SCAN command it can be used still and > indeed probably for a long time. I just wanted to point out that it is > not recommended for new user-space functionality. We used to do it more, but most features are more complex than "command is supported" or are simpler than "these 5 commands are supported" (just a single bit to indicate the whole feature is enough), so we mostly use extended feature flags now. > > It sometimes feels like wpa_supplicant gets treated as a static entity > > that can never be changed. In fact, send a patch to Jouni implementing > > the best practice, with a fallback to preserve compat for old kernels, > > and I'm sure he'd entertain it. Just because the supplicant does > > something a certain way, doesn't mean it's the *best* way, but it too > > evolves. You also need to consider old supplicant on new kernels though? But I didn't really follow this part of the discussion, so you're probably taking that into account. johannes
