From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Hans de Goede <hdegoede@redhat.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time
Date: Wed, 8 Mar 2017 11:15:35 +0100 [thread overview]
Message-ID: <edc0f67d-59d7-437c-2588-e895217577cd@broadcom.com> (raw)
In-Reply-To: <d0bec61e-4481-42b9-fcdd-d6a8f8f3524e@broadcom.com>
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 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 provision firmware.
>>> Can you explain the scenario here?
>>
>> I'm not doing anything special just connecting to my isp provided
>> accesspoint
>> using NetworkManager.
>
> Ok. So it is probably the P2P_DEVICE interface as that is the only
> interface being created in that scenario. Can you provide a log with
> brcmfmac driver debug=0x1416.
I guess you are seeing this with 43362. Is that correct?
Regards,
Arend
next prev parent reply other threads:[~2017-03-08 10:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 21:45 [PATCH v2 1/4] brcmfmac: Do not print the firmware version as an error Hans de Goede
2017-02-27 21:45 ` [PATCH v2 2/4] brcmfmac: p2p and normal ap access are not always possible at the same time Hans de Goede
2017-03-07 10:03 ` Arend Van Spriel
2017-03-08 8:24 ` Hans de Goede
2017-03-08 9:26 ` Arend Van Spriel
2017-03-08 10:15 ` Arend Van Spriel [this message]
2017-03-08 11:16 ` Hans de Goede
2017-03-10 8:08 ` Hans de Goede
2017-03-10 9:35 ` Arend Van Spriel
2017-03-16 11:51 ` Hans de Goede
2017-02-27 21:45 ` [PATCH v2 3/4] brcmfmac: Do not complain about country code "00" Hans de Goede
2017-03-07 10:04 ` Arend Van Spriel
2017-02-27 21:45 ` [PATCH v2 4/4] brcmfmac: Handle status == BRCMF_E_STATUS_ABORT in cfg80211_escan_handler Hans de Goede
2017-03-07 10:06 ` Arend Van Spriel
2017-03-07 9:59 ` [PATCH v2 1/4] brcmfmac: Do not print the firmware version as an error Arend Van Spriel
2017-03-08 8:23 ` Hans de Goede
2017-03-08 9:28 ` Arend Van Spriel
2017-03-08 9:57 ` Kalle Valo
2017-03-08 10:08 ` Hans de Goede
2017-03-08 10:13 ` Arend Van Spriel
2017-03-08 10:14 ` Kalle Valo
2017-03-07 14:30 ` Kalle Valo
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=edc0f67d-59d7-437c-2588-e895217577cd@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tiwai@suse.de \
/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