Return-path: Received: from mout.kundenserver.de ([212.227.126.131]:54227 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750815AbdHKF4c (ORCPT ); Fri, 11 Aug 2017 01:56:32 -0400 Subject: Re: brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W To: Arend van Spriel Cc: Franky Lin , brcm80211-dev-list.pdl@broadcom.com, linux-wireless@vger.kernel.org, Pieter-Paul Giesberts , Kalle Valo , linux-rpi-kernel@lists.infradead.org, Hante Meuleman , Ian Molton References: <384537059.123625.1498678388857@email.1und1.de> <1133935948.74840.1500297053336@email.1und1.de> <1389331679.85833.1500323470395@email.1und1.de> <314866679.136055.1501049965582@email.1und1.de> <597857D6.4010508@broadcom.com> From: Stefan Wahren Message-ID: <683db4ef-662f-3ef2-f69a-c78ca8297115@i2se.com> (sfid-20170811_075636_612655_6F9B3665) Date: Fri, 11 Aug 2017 07:55:42 +0200 MIME-Version: 1.0 In-Reply-To: <597857D6.4010508@broadcom.com> Content-Type: text/plain; charset=utf-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Arend, Am 26.07.2017 um 10:50 schrieb Arend van Spriel: > On 7/26/2017 8:19 AM, Stefan Wahren wrote: >> Hi, >> >> >> what are the plans to fix this regression? > > I am a bit in doubt about this one. We can avoid the firmware config > above for bcm4343x devices as a short term fix. However, I would like > to root cause the issue. Received a Pi Zero over here so gearing it up. > > Regards, > Arend > is there an update about this issue? Should i prepare such a short term fix? Regards Stefan