From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hante Meuleman <meuleman@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/7] brcmfmac: nvram loading and code rework
Date: Thu, 20 Aug 2015 21:41:48 +0200 [thread overview]
Message-ID: <55D62D7C.8000304@broadcom.com> (raw)
In-Reply-To: <CACna6rxVuhgea8C7KeWbfv31qGn=n=MxnJ+HBW2FHcVbviiYgQ@mail.gmail.com>
On 08/20/2015 05:51 PM, Rafał Miłecki wrote:
> On 20 August 2015 at 12:23, Arend van Spriel <arend@broadcom.com> wrote:
>> On 08/20/2015 01:06 AM, Rafał Miłecki wrote:
>>>
>>> On 12 August 2015 at 10:58, Arend van Spriel <arend@broadcom.com> wrote:
>>>>
>>>> You did a warm reboot of the device, right? There seems to be an issue
>>>> because on OpenWrt the brcmfmac is not unloaded upon warm reboot, which
>>>> makes the device unaccessible. Because on OpenWrt the firmware request is
>>>> synchronous (OpenWrt patch on top of upstream brcmfmac) it results in
>>>> probe
>>>> failing on invalid access making the issue OpenWrt specific. Hante
>>>> created a
>>>> fix for the warm reboot issue.
>>>
>>>
>>> Hante could you share your fix?
>>
>>
>> Hi Rafał,
>>
>> Just sent you the patch privately.
>
> Seems to be working nice, thanks! I hope you'll be able to publish it soon :)
Not before monday and I suspect a merge window coming up, but I might be
just paranoid ;-)
Regards,
Arend
prev parent reply other threads:[~2015-08-20 19:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 18:31 [PATCH 0/7] brcmfmac: nvram loading and code rework Arend van Spriel
2015-07-10 18:31 ` [PATCH 1/7] brcmfmac: Add support for host platform NVRAM loading Arend van Spriel
2015-07-11 17:09 ` Rafał Miłecki
2015-08-19 21:21 ` [PATCH v2 " Arend van Spriel
2015-08-19 21:43 ` Arend van Spriel
2015-08-20 15:53 ` Rafał Miłecki
2015-08-20 16:06 ` Arend van Spriel
2015-08-20 16:21 ` Rafał Miłecki
2015-08-20 15:59 ` Rafał Miłecki
2015-08-20 16:14 ` Arend van Spriel
2015-07-10 18:31 ` [PATCH 2/7] brcmfmac: correct interface combination info Arend van Spriel
2015-07-10 18:31 ` [PATCH 3/7] brcmfmac: Increase nr of supported flowrings Arend van Spriel
2015-07-10 18:31 ` [PATCH 4/7] brcmfmac: add debugfs entry for msgbuf statistics Arend van Spriel
2015-07-10 18:31 ` [PATCH 5/7] brcmfmac: make use of cfg80211_check_combinations() Arend van Spriel
2015-07-10 18:31 ` [PATCH 6/7] brcmfmac: consolidate ifp lookup in driver core Arend van Spriel
2015-07-10 18:31 ` [PATCH 7/7] brcmfmac: block the correct flowring when backup queue overflow Arend van Spriel
2015-07-19 15:05 ` [PATCH 0/7] brcmfmac: nvram loading and code rework Rafał Miłecki
2015-07-20 17:14 ` Arend van Spriel
2015-07-23 16:02 ` Kalle Valo
2015-07-26 11:08 ` Arend van Spriel
2015-07-26 12:08 ` Kalle Valo
2015-07-26 15:40 ` Rafał Miłecki
2015-08-12 8:58 ` Arend van Spriel
2015-08-12 14:07 ` Rafał Miłecki
2015-08-19 14:58 ` Rafał Miłecki
2015-08-19 23:06 ` Rafał Miłecki
2015-08-20 10:23 ` Arend van Spriel
2015-08-20 15:51 ` Rafał Miłecki
2015-08-20 19:41 ` Arend van Spriel [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=55D62D7C.8000304@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=zajec5@gmail.com \
/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).