From: Johannes Berg <johannes@sipsolutions.net>
To: Ujjal Roy <royujjal@gmail.com>
Cc: David Herrmann <dh.herrmann@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] P2P setup timeout
Date: Tue, 17 Dec 2013 08:19:57 +0100 [thread overview]
Message-ID: <1387264797.4749.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <52AFE619.1060104@gmail.com> (sfid-20131217_065027_262928_A0D43F31)
On Tue, 2013-12-17 at 11:20 +0530, Ujjal Roy wrote:
> Hi Johannes,
>
> On 12/16/2013 07:15 PM, Johannes Berg wrote:
> > On Mon, 2013-12-16 at 14:39 +0100, David Herrmann wrote:
> >
> > Right, and I suspect they don't get a response because (as the sniffer
> > trace tells me) they're sent with 1 Mbps (a CCK rate), which is invalid
> > in the P2P spec (must use OFDM).
> >
>
> Can you please let me know, is the P2P spec freely available to read or
> download? If so, please provide some info from where I can able to get
> the document. Actually, I need to know - how to add P2P_DEVICE support
> in a driver.
No, it isn't. However, P2P_DEVICE support is not described in the spec
anyway since it's a Linux thing.
johannes
prev parent reply other threads:[~2013-12-17 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:18 [BUG] P2P setup timeout David Herrmann
2013-12-09 14:03 ` Oleksij Rempel
2013-12-09 14:30 ` David Herrmann
2013-12-16 12:00 ` David Herrmann
2013-12-16 12:36 ` Johannes Berg
2013-12-16 13:39 ` David Herrmann
2013-12-16 13:45 ` Johannes Berg
2013-12-16 13:51 ` David Herrmann
2013-12-16 14:57 ` Oleksij Rempel
2013-12-16 15:09 ` David Herrmann
2013-12-16 15:15 ` Johannes Berg
2013-12-16 15:26 ` Oleksij Rempel
2013-12-16 15:29 ` Johannes Berg
2013-12-16 15:37 ` Oleksij Rempel
2013-12-16 15:53 ` David Herrmann
2013-12-17 5:50 ` Ujjal Roy
2013-12-17 7:19 ` 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=1387264797.4749.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dh.herrmann@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=royujjal@gmail.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;
as well as URLs for NNTP newsgroup(s).