From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] wireless: cfg80211: add peer-to-peer related definitions
Date: Thu, 11 Oct 2012 20:05:04 +0200 [thread overview]
Message-ID: <50770A50.3010305@broadcom.com> (raw)
In-Reply-To: <1349976385.13097.13.camel@jlt4.sipsolutions.net>
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
next prev parent reply other threads:[~2012-10-11 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 14:18 [RFC] wireless: cfg80211: add peer-to-peer related definitions Arend van Spriel
2012-10-11 16:41 ` Johannes Berg
2012-10-11 17:23 ` Arend van Spriel
2012-10-11 17:26 ` Johannes Berg
2012-10-11 18:05 ` Arend van Spriel [this message]
2012-10-11 19:34 ` Johannes Berg
2012-10-16 17:06 ` Arend van Spriel
2012-10-11 16:42 ` Johannes Berg
2012-10-11 17:24 ` Arend van Spriel
2012-10-11 17:29 ` Arend van Spriel
2012-10-11 17:46 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50770A50.3010305@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).