Thread (21 messages) 21 messages, 3 authors, 2018-03-02

Re: [PATCH resend] brcmfmac: p2p and normal ap access are not always possible at the same time

From: Arend van Spriel <arend.vanspriel@broadcom.com>
Date: 2017-08-04 12:35:32

On 5/26/2017 12:57 PM, Hans de Goede wrote:
The firmware responding with -EBUSY when trying to add an extra virtual-if
is a normal thing, do not print an error for this.
Hi Hans,

First of all, sorry! This one is long overdue (thanks for the reminder, 
Kalle). Not sure what the claim is here. I have to check the firmware to 
see what could make this fail. Thing is that wpa_supplicant will try to 
create the interface upon startup and it is really required for P2P 
operations. Now people not using that will probably not care about the 
failure, but I would like to find out why it is failing. wpa_supplicant 
will not do a retry upon -EBUSY.

With which firmware (target string and version) are you seeing this so I 
know where to dive in.

Regards,
Arend
Signed-off-by: Hans de Goede <redacted>
---
  .../net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c    | 14 ++++++++++----
  drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c     |  5 ++++-
  2 files changed, 14 insertions(+), 5 deletions(-)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help