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: Tue, 19 Mar 2013 21:27:46 +0100 [thread overview]
Message-ID: <1363724866.8336.22.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <3959922.dEpYdEMVAq@lx-vladimir>
On Tue, 2013-03-19 at 19:35 +0200, Vladimir Kondratiev wrote:
> > I was under the impression that wpa_s allowed "progressive" (i.e.
> one
> > non-social channel per iteration) even in find? I could be wrong
> though,
> > maybe only in search.
> wpa_s do it in that "legacy" scan before find phase
No: p2p_find type=progressive
If this will no longer be supported, I guess you can say so. I also
don't really see how the API could support it, but it is a potential
issue.
> > Ok, but can you also document what the driver should add? Supported
> > rates, HT info, ... presumably?
>
> It is same case as for 'scan' or 'start_ap' - driver expect to deal
> with
> IE's same way. There we don't say anything, why do it here?
Maybe we're better now? ;-)
I guess I'm not too concerned about this.
> Anything more I expected to do with patch? Or, is it on its way to
> your git?
Send as [PATCH] for sure, but we should think about the progressive
thing.
johannes
next prev parent reply other threads:[~2013-03-19 20:27 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 [this message]
2013-03-15 15:51 ` Johannes Berg
2013-03-07 10:01 ` 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=1363724866.8336.22.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.