From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
Cc: "Luis R . Rodriguez" <rodrigue@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC] P2P find offload
Date: Thu, 07 Mar 2013 11:01:39 +0100 [thread overview]
Message-ID: <1362650499.8694.15.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1686131.738LDv7O6j@lx-vladimir>
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
prev parent reply other threads:[~2013-03-07 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 12:24 [RFC] P2P find offload Vladimir Kondratiev
2013-03-04 15:47 ` Johannes Berg
2013-03-07 7:10 ` Vladimir Kondratiev
2013-03-07 9:31 ` Vladimir Kondratiev
2013-03-07 10:08 ` Johannes Berg
2013-03-07 10:11 ` Johannes Berg
2013-03-07 14:10 ` Vladimir Kondratiev
2013-03-10 15:43 ` Vladimir Kondratiev
2013-03-15 18:40 ` Johannes Berg
2013-03-17 8:56 ` Vladimir Kondratiev
2013-03-18 20:31 ` Johannes Berg
[not found] ` <3959922.dEpYdEMVAq@lx-vladimir>
2013-03-19 20:27 ` Johannes Berg
2013-03-15 15:51 ` Johannes Berg
2013-03-07 10:01 ` Johannes Berg [this message]
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=1362650499.8694.15.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--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