All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: Arend van Spriel <arend@broadcom.com>
Cc: Arend van Spriel <aspriel@gmail.com>,
	"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, 23 Jul 2015 13:05:59 +0200	[thread overview]
Message-ID: <1437649559.15337.1.camel@embedded.rocks> (raw)
In-Reply-To: <1436255260.27716.6.camel@embedded.rocks>

Hi all,

On Di, 2015-07-07 at 09:47 +0200, Jörg Krause wrote:
> Hi Arend,
> 
> On Di, 2015-06-23 at 14:08 +0200, Arend van Spriel wrote:
> > On 06/23/15 13:31, Jörg Krause wrote:
> > > Hi Arend,
> > > 
> > > On So, 2015-06-21 at 23:18 +0200, Arend van Spriel wrote:
> > > > 
> > > > My bad. The patch removes p2pdev from interface modes, but it 
> > > > is
> > > > still
> > > > listed in the interface combinations and cfg80211 will complain 
> > > > 
> > > > about
> > > > it. Have to extend the patch. I better do that after a good 
> > > > nights
> > > > sleep.
> > > 
> > > Never mind! Did you had a good night sleep already :-) ?
> > 
> > Several ;-) Did not get to this earlier. Thanks for the reminder.
> > 
> > Had a closer look at wiphy_verify_combinations() and I am hopeful 
> > the 
> > 
> > attached patch will fix the wiphy_register() failure.
> > 
> 
> Sorry for late reply! I was busy on another topic...
> 
> I've applied your patch, but p2p interface is still not working. I
> attached the debug log from wpa_supplicant.
> 
> I tested with Linux Kernel 4.0.7 and wpa_supplicant 2.4.
> 
> This is my p2p_supplicant.conf:
>     ctrl_interface=/var/run/p2p_supplicant
>     update_config=1
> 
>     device_name=HBM10
>     device_type=1-0050F204-1
> 
>     p2p_go_ht40=1
> 
> Test with the p2p_find command:
>     # wpa_cli -p /var/run/p2p_supplicant p2p_find
>     Selected interface 'p2p0'
>     1928.165036: p2p0: Control interface command 'P2P_FIND'
>     FAIL
> 

ping :-) Any news on this?

Best regards
Jörg Krause

      reply	other threads:[~2015-07-23 11:06 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
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 [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=1437649559.15337.1.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --cc=arend@broadcom.com \
    --cc=aspriel@gmail.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 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.