Re: [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time

On 10-3-2017 9:08, Hans de Goede wrote: > Hi, > > On 08-03-17 12:16, Hans de Goede wrote: >> Hi, >> >> On 08-03-17 11:15, Arend Van Spriel wrote: >>> On 8-3-2017 10:26, Arend Van Spriel wrote: On 8-3-2017 9:24, Hans de Goede wrote: > Hi, > > On 07-03-17 11:03, Arend Van Spriel wro

Re: [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time

Hi, On 08-03-17 11:15, Arend Van Spriel wrote: On 8-3-2017 10:26, Arend Van Spriel wrote: On 8-3-2017 9:24, Hans de Goede wrote: Hi, On 07-03-17 11:03, Arend Van Spriel wrote: On 27-2-2017 22:45, Hans de Goede wrote: The firmware responding with -EBUSY when trying to add an extra virtual-

Re: [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time

On 8-3-2017 9:24, Hans de Goede wrote: > Hi, > > On 07-03-17 11:03, Arend Van Spriel wrote: >> >> >> On 27-2-2017 22:45, 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. >> >> This may be

Re: [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time

On 8-3-2017 10:26, Arend Van Spriel wrote: > On 8-3-2017 9:24, Hans de Goede wrote: >> Hi, >> >> On 07-03-17 11:03, Arend Van Spriel wrote: >>> >>> >>> On 27-2-2017 22:45, Hans de Goede wrote: The firmware responding with -EBUSY when trying to add an extra virtual-if is a normal thin

Re: [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time

Hi, On 07-03-17 11:03, Arend Van Spriel wrote: On 27-2-2017 22:45, 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. This may be something we need to look into. It seems to me the interface comb

Re: [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time

On 27-2-2017 22:45, 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. This may be something we need to look into. It seems to me the interface combinations needs to be fixed so we do not try to p

[PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time

The firmware responding with -EBUSY when trying to add an extra virtual-if is a normal thing, do not print an error for this. Signed-off-by: Hans de Goede --- .../net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c| 14 ++ drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c