From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Franky Lin <franky.lin@broadcom.com>,
brcm80211-dev-list.pdl@broadcom.com,
linux-wireless@vger.kernel.org,
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-rpi-kernel@lists.infradead.org,
Hante Meuleman <hante.meuleman@broadcom.com>,
Ian Molton <ian@mnementh.co.uk>
Subject: Re: brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W
Date: Fri, 11 Aug 2017 10:24:10 +0200 [thread overview]
Message-ID: <598D69AA.6070206@broadcom.com> (raw)
In-Reply-To: <683db4ef-662f-3ef2-f69a-c78ca8297115@i2se.com>
On 8/11/2017 7:55 AM, Stefan Wahren wrote:
> 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?
This got a bit snowed under. Thanks for the reminder. I will prepare the
short term fix shortly.
Regards,
Arend
next prev parent reply other threads:[~2017-08-11 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 19:33 brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W Stefan Wahren
2017-07-17 13:10 ` Stefan Wahren
2017-07-17 19:50 ` Franky Lin
2017-07-17 20:31 ` Stefan Wahren
2017-07-26 6:19 ` Stefan Wahren
2017-07-26 8:50 ` Arend van Spriel
2017-08-11 5:55 ` Stefan Wahren
2017-08-11 8:24 ` Arend van Spriel [this message]
2017-07-18 8:59 ` James Hughes
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=598D69AA.6070206@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=ian@mnementh.co.uk \
--cc=kvalo@codeaurora.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=stefan.wahren@i2se.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.