On Thu, 2013-03-07 at 09:10 +0200, Vladimir Kondratiev wrote: > > We had something like this before. I think you need to specify not the > > wiphy but a netdev though, to know what MAC address to use. In fact, not > > a netdev but a wdev, so it can work on P2P_Device type wdevs. > Why do we need wdev here? It should be similar to scan, as p2p scan composed > of legacy scan and p2p find. Scan have only wiphy. > It's no problem to add wdev as well, of course. I'll add it. No, scan also has the device? It is needed for the MAC address, of course. > > Also, timings? Or is that left to the driver? > Yes, timing is up to the driver. Point is, firmware may have its reasons > when switch search/listen phases. Some hints from userspace might be helpful though? > > wpa_s will need to know whether or not it responded, unless you mandate > > that it must respond by itself -- not sure if you should do that though? > Same way as today wpa_s know whether driver/firmware answer probes - > WIPHY_FLAG_AP_PROBE_RESP_OFFLOAD. Or, should I add one more flag, like > WIPHY_FLAG_P2P_PROBE_RESP_OFFLOAD? AP_PROBE_RESP_OFFLOAD doesn't seem appropriate? just read out the name aloud, it starts with "AP" ;-) johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
