On Mon, 2020-06-01 at 18:32 -0700, Brian Norris wrote: > I haven't quite reached the 3 month lag on the prior replies here :) But I did, almost ;-) > I do want to see this question resolved somehow, or else we'll be > dragging along out-of-tree patches for...(counts on fingers)...4 > different nl80211 APIs for the same feature, and a driver-detecting > user space for it. Right. > I think I was half-hoping that we'd get to chat at > netdev about this, but that's not happening any time soon. (Topic for > another day: does a "wireless workshop" still happen at a virtual-only > conference?) Yes, but only a short 1.5hr video call I guess. I'm not even sure what to do there yet. [snip] Thanks for the overview! > Also, Kalle had some concerns about stable ABI questions: shouldn't we > bake in some kind of "check for support" feature to these kinds of > APIs [3]? That would help ease transition, if we do start with a > vendor API and move to a common one in the future. Given the nature of > this feature, I wouldn't expect there will be a large variety of users > making use of the APIs -- and I, for one, would be happy to migrate my > user space over some period of time, as needed. We do that? We list out the available vendor APIs, and in most cases (perhaps not the one you've noticed there) we also list out the availability of real nl80211 APIs in some way. johannes
