linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: brcmfmac: Failed to create interface p2p-dev-p2p0: -28 (No space left on device)
Date: Thu, 18 Jun 2015 08:13:38 +0200	[thread overview]
Message-ID: <1434608018.5481.4.camel@embedded.rocks> (raw)
In-Reply-To: <55803214.2030204@broadcom.com>

Hi Arend,

On Di, 2015-06-16 at 16:26 +0200, Arend van Spriel wrote:
> On 06/16/15 11:59, Jörg Krause wrote:
> > Hi Arend,
> > 
> > as I wrote in my previous mail ("brcmfmac: brcmf_p2p_create_p2pdev:
> > timeout occurred") I get a p2p0 interface when loading the brcmfmac
> > module with p2pon=1 (Linux kernel 4.0.5, BCM43362).
> > 
> > Unfortunatly, if I try to use the p2p0 interface with 
> > wpa_supplicant
> > 2.4 I get an error:
> > 
> >      Failed to create interface p2p-dev-p2p0: -28 (No space left on
> >      device)
> >      nl80211: Failed to create a P2P Device interface p2p-dev-p2p0
> >      P2P: Failed to enable P2P Device interface
> 
> Using p2pon=1 is old-school p2p, ie. it creates a regular netdev for 
> doing p2p management stuff. Problem is that brcmfmac also indicates 
> p2p 
> device support. We can remove p2pon parameter or not indicate p2p dev 
> 
> support when p2pon=1.

I used p2pon because the p2p0 interface is not created without it. It
fails with the error message "brcmf_p2p_create_p2pdev: timeout
occurred" as written in my previous mails. I would prefer not to use
it, so maybe we can find a solution how to get it working without it.

> 
> Can you patch brcmfmac and give it a try. Need to start 
> wpa_supplicant 
> for two interface and if I recall correctly p2p0 must be specified 
> first.

Can you give me a hint where to patch brcmfmac. Many thanks!

Best regards
Jörg Krause

  reply	other threads:[~2015-06-18  6:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 12:35 brcmfmac: brcmf_p2p_create_p2pdev: timeout occurred Jörg Krause
2015-06-08 12:41 ` Arend van Spriel
2015-06-08 12:56   ` Jörg Krause
2015-06-08 13:48   ` Jörg Krause
2015-06-08 16:46     ` Arend van Spriel
2015-06-08 20:17       ` Jörg Krause
2015-06-08 21:14         ` Arend van Spriel
2015-06-08 21:19           ` Jörg Krause
2015-06-16  9:59           ` brcmfmac: Failed to create interface p2p-dev-p2p0: -28 (No space left on device) Jörg Krause
2015-06-16 14:26             ` Arend van Spriel
2015-06-18  6:13               ` Jörg Krause [this message]
2015-06-18  8:27                 ` Arend van Spriel
2015-06-18 20:07                   ` Jörg Krause
2015-06-21 21:18                     ` Arend van Spriel
2015-06-23 11:31                       ` Jörg Krause
2015-06-23 12:08                         ` Arend van Spriel
2015-07-07  7:47                           ` Jörg Krause
2015-07-23 11:05                             ` Jörg Krause

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=1434608018.5481.4.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --cc=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --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).