On Tue, Dec 13, 2016 at 8:06 AM, Johannes Berg <[email protected]> wrote: > >> Supporting requests (or more precisely requests and results) >> differentiated by user-space entity can be tricky. Right now we are >> not checking current caller pid, right? Maybe it is also good idea - >> or maybe we can just make result filtering per user-space caller? > > Could be done. > > You seem to be very worried about the partial results - I'm not too > worried about that I guess, the connection manager itself will always > be able to wait for the full scan to finish before making a decision, > but it may not even want to (see the separate discussion on per-channel > "done" notifications etc.)
Probably you are right. > I'm much more worried about the "bucket reporting" since that doesn't > fit into the current full BSS reporting model at all. What's your > suggestion for this? > > johannes We can either use alternative structure in kernel wireless stack, or alternative structure in userspace (in wpa_supplicant), and we will most likely need special command for this case at least to retrieve results.
