From: Arend van Spriel <arend@broadcom.com>
To: Ochal Christophe <christophe.ochal@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Broadcom 43340
Date: Sat, 14 Mar 2015 20:54:02 +0100 [thread overview]
Message-ID: <550491DA.6030105@broadcom.com> (raw)
In-Reply-To: <55048BB1.9080906@gmail.com>
+ linux-wireless
On 03/14/15 20:27, Ochal Christophe wrote:
> Dear Sir,
>
> On 03/14/2015 08:12 PM, Arend van Spriel wrote:
>> The nvram file is board specific and so Asus should be able to provide
>> that. What OS does Asus provide on this eee book? The firmware file
>> will be submitted to linux-firmware soon, but in the mean time you can
>> also find it in Android repository [1]. Just rename the file
>> fw_43341.bin to brcmfmac43340-sdio.bin.
>>
>> Regards,
>> Arend
>>
>> [1]
>> https://android.googlesource.com/platform/hardware/broadcom/wlan/+/master/bcmdhd/firmware/bcm43341/
>>
>
> Thank you for the link, the Asus eebook x205ta comes with Windows 8.1,
> no idea how I'm going to get Asus to deliver that nvram, but at least
> I'm halfway there now, the firmware loads correctly.
For Windows 8.1 the nvram file is stored in EFI variable space. This is
accessible in Linux as well. If I recall correctly it should be in
/sys/firmware/efi/efivars. There should be a file named nvram-*. Copy
that to /lib/firmware/brcm/brcmfmac43340-sdio.txt.
Regards,
Arend
next parent reply other threads:[~2015-03-14 19:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <550482A2.3080803@gmail.com>
[not found] ` <55048833.90408@broadcom.com>
[not found] ` <55048BB1.9080906@gmail.com>
2015-03-14 19:54 ` Arend van Spriel [this message]
2015-03-14 20:07 ` Broadcom 43340 Ochal Christophe
2015-03-14 20:39 ` Stefan Lippers-Hollmann
2015-03-14 22:13 ` Ochal Christophe
2015-03-15 11:37 ` Arend van Spriel
2015-03-15 20:38 ` Jürgen Bausa
2015-03-15 21:14 ` Arend van Spriel
2015-03-17 21:01 ` Jürgen Bausa
2015-03-17 22:20 ` Arend van Spriel
2015-03-18 21:12 ` Jürgen Bausa
2015-03-17 23:20 ` Dan Williams
2015-03-18 21:24 ` Jürgen Bausa
2015-03-18 21:29 ` Dan Williams
2015-03-18 21:40 ` Arend van Spriel
2015-03-19 21:00 ` Jürgen Bausa
2015-03-19 21:40 ` Arend van Spriel
2015-03-21 20:38 ` Jürgen Bausa
2015-03-22 13:11 ` Arend van Spriel
2015-03-22 20:14 ` Jürgen Bausa
2015-03-23 9:52 ` Arend van Spriel
2015-03-23 20:09 ` Jürgen Bausa
2015-03-23 20:50 ` Arend van Spriel
2015-03-15 21:20 ` Stefan Lippers-Hollmann
2015-03-15 2:03 ` Koen Bulcke
2015-03-15 11:39 ` Arend van Spriel
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=550491DA.6030105@broadcom.com \
--to=arend@broadcom.com \
--cc=christophe.ochal@gmail.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 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.