From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, "Jouni Malinen" <j@w1.fi>
Subject: Re: [RFC] wireless: cfg80211: add peer-to-peer related definitions
Date: Tue, 16 Oct 2012 19:06:49 +0200 [thread overview]
Message-ID: <507D9429.7040105@broadcom.com> (raw)
In-Reply-To: <1349984058.13097.17.camel@jlt4.sipsolutions.net>
On 10/11/2012 09:34 PM, Johannes Berg wrote:
> On Thu, 2012-10-11 at 20:05 +0200, Arend van Spriel wrote:
>
>>> Ah, fmac, that will be somewhat interesting. What userspace APIs are you
>>> proposing for that case?
>
>> 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.
>
> Well the APIs that we have in place right now are really basically just
> a conduit and wpa_s does all the operations. I would expect fmac to have
> more offloads (and thus need the parsing), I'd actually be surprised if
> you could work with the existing APIs.
I mainly focussed on reworking brcmfmac to support multiple (virtual)
interfaces and wireless devices without netdev. So far I only did the
scanning part of p2p device discovery which is a regular 802.11 scan so
no API change needed there. So no API change proposals yet. When I learn
more I will discuss it on the wireless list.
Gr. AvS
next prev parent reply other threads:[~2012-10-16 17: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
2012-10-11 19:34 ` Johannes Berg
2012-10-16 17:06 ` Arend van Spriel [this message]
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=507D9429.7040105@broadcom.com \
--to=arend@broadcom.com \
--cc=j@w1.fi \
--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).