On 10/11/2012 07:26 PM, Johannes Berg wrote:
On Thu, 2012-10-11 at 19:23 +0200, Arend van Spriel wrote:
Looks ok ... but why would a driver need to parse P2P stuff? For NoA for
example maybe?
I did not yet go through a lot of the P2P code that is on my plate to
port upstream, but one item that is extracted in the part I already did
is the P2P listen channel. I just wanted to do this RFC before sending
out the brcmfmac code patches that actually is using it. This change
will be part of that patch series.
Ah, fmac, that will be somewhat interesting. What userspace APIs are you
proposing for that case?
Hi Johannes,
Not sure if I understand the question. I am using wpa_supplicant with
wpa_cli for testing and given its p2p support I assumed there is already
a nl80211 api in place. I am still trying to get a good sense on it. The
P2P code to port does more parsing of P2P stuff and if you mean adding
userspace APIs to avoid just that I would definitely prefer that.
Gr. AvS
--
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
