From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "Peer, Ilan" <ilan.peer@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
Jouni Malinen <jouni@qca.qualcomm.com>
Subject: Re: [PATCH v8] cfg80211: P2P find phase offload
Date: Tue, 04 Jun 2013 14:07:36 +0200 [thread overview]
Message-ID: <1370347656.8287.15.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <2446389.or6hSZ58yP@lx-vladimir>
> > > +struct cfg80211_p2p_find_params {
> >
> > The parameters are missing the listen channel (which is needed to the listen phase).
>
> There are n_channels and channels that define set of social channels
> to operate on. It applies to both listen and search.
I don't think that's true -- you only respond on the listen channel but
send probe requests on all the channels?
> > > + attr = info->attrs[NL80211_ATTR_IE_PROBE_RESP];
> > > + if (attr) {
> > > + params.probe_resp_ie_len = nla_len(attr);
> > > + params.probe_resp_ie = nla_data(attr);
> > > + }
> >
> > Is it valid to get Probe response IEs even if the driver did not report support for it?
>
> One can't do p2p_find if it does not reply to P2P discovery probes.
> It is unrelated to answering probes in AP mode - driver may leave this
> to supplicant.
I think what Ilan is asking is whether you should reject the probe_resp
attribute if NL80211_FEATURE_P2P_PROBE_RESP_OFFLOAD isn't set. I'm fine
with just ignoring it (as is done now) though, might make wpa-s easier.
johannes
next prev parent reply other threads:[~2013-06-04 12:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 6:44 [PATCH v8] P2P find phase offload Vladimir Kondratiev
2013-06-04 6:44 ` [PATCH v8] cfg80211: " Vladimir Kondratiev
2013-06-04 10:07 ` Peer, Ilan
2013-06-04 11:24 ` Vladimir Kondratiev
2013-06-04 12:07 ` Johannes Berg [this message]
2013-06-04 14:03 ` Vladimir Kondratiev
2013-06-04 14:29 ` Johannes Berg
2013-06-04 14:35 ` Malinen, Jouni
2013-06-04 16:47 ` Vladimir Kondratiev
2013-06-04 18:30 ` Jouni Malinen
2013-06-05 7:10 ` Vladimir Kondratiev
2013-06-05 7:53 ` Johannes Berg
2013-06-05 13:30 ` Vladimir Kondratiev
2013-06-11 12:12 ` Johannes Berg
2013-06-05 7:46 ` Johannes Berg
2013-06-05 8:10 ` Arend van Spriel
2013-06-05 8:18 ` Johannes Berg
2013-06-05 8:38 ` Arend van Spriel
2013-06-05 16:26 ` Vladimir Kondratiev
2013-06-05 8:12 ` Jouni Malinen
2013-06-04 12:10 ` Peer, Ilan
2013-06-04 10:43 ` Johannes Berg
2013-06-04 6:51 ` [PATCH v8] " 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=1370347656.8287.15.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilan.peer@intel.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
/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