From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BCM4356 does not initalize after firmware update
Date: Wed, 20 Dec 2017 11:15:03 +0100 [thread overview]
Message-ID: <20171220101502.GA25414@redhat.com> (raw)
In-Reply-To: <5A3A2383.1080103@broadcom.com>
Hi
On Wed, Dec 20, 2017 at 09:46:59AM +0100, Arend van Spriel wrote:
> I had my colleague run some tests as he has the device, but he is an ocean
> away. So he could get the new firmware running with nvram file. For the old
> firmware the device could boot without nvram, but the scan results were
> showing that the device was not operating optimally. Could you try the new
> firmware with the attached sample nvram file and let me know if that works
> for you?
Yes. After placing the nvram file to /lib/firmware/brcm/brcmfmac4356-pcie.txt
device now initalize with the new firmware. Is this right fix, IOW should this
file be shiped in linux-firmware ?
Thanks
Stanislaw
prev parent reply other threads:[~2017-12-20 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 16:12 BCM4356 does not initalize after firmware update Stanislaw Gruszka
2017-12-14 9:13 ` Arend van Spriel
2017-12-14 14:22 ` Stanislaw Gruszka
2017-12-15 9:58 ` Arend van Spriel
2017-12-15 10:32 ` Stanislaw Gruszka
2017-12-15 11:10 ` Arend van Spriel
2017-12-15 12:20 ` Stanislaw Gruszka
2017-12-19 11:36 ` Arend van Spriel
2017-12-19 12:23 ` Stanislaw Gruszka
2017-12-20 8:46 ` Arend van Spriel
2017-12-20 10:15 ` Stanislaw Gruszka [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=20171220101502.GA25414@redhat.com \
--to=sgruszka@redhat.com \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
/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).