On Mon, 2019-01-28 at 10:19 +0530, Karthikeyan Periyasamy wrote: > > At the same time, what happens today actually? Do all frames from non- > > associated clients come up to the host? If so, is this not a problem > > for all APs, not just ath10k? > > Today, without this patch. No frames from non-associated clients come up > to the host in AP mode. So it's not just _filtering_ but also enabling to see them, right? > > And if they don't come up, what feature requires this? Sorry for the > > vague questions, but I'm not really sure what this is all about. If > > there's a need for these frames, wouldn't we need a generic way of > > enabling receiving them, and perhaps even signalling hostapd with them? > > Steering application use this feature in their logical part of client > steering. But there aren't even any steering applications that are open source or anything like that, right? I don't see why we should include this upstream. Clearly you can use this for whatever you like to do with your driver in non-upstream builds, and you can open-source this code, but if there are no applications that could possibly use it upstream why bother? johannes
