From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-gw1-out.broadcom.com ([216.31.210.62]:50299 "EHLO mail-gw1-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750714AbbHTKXh (ORCPT ); Thu, 20 Aug 2015 06:23:37 -0400 Message-ID: <55D5AAA5.1080700@broadcom.com> (sfid-20150820_122340_634824_6633AB0A) Date: Thu, 20 Aug 2015 12:23:33 +0200 From: Arend van Spriel MIME-Version: 1.0 To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Hante Meuleman CC: Kalle Valo , linux-wireless Subject: Re: [PATCH 0/7] brcmfmac: nvram loading and code rework References: <1436553071-32423-1-git-send-email-arend@broadcom.com> <55AD2C8F.9010509@broadcom.com> <55CB0ACA.3000109@broadcom.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 08/20/2015 01:06 AM, Rafał Miłecki wrote: > On 12 August 2015 at 10:58, Arend van Spriel 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. Regards, Arend