From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
To: Ochal Christophe <christophe.ochal@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Broadcom 43340
Date: Sat, 14 Mar 2015 21:39:07 +0100 [thread overview]
Message-ID: <20150314213907.3f1167bb@mir> (raw)
In-Reply-To: <55049507.6040209@gmail.com>
Hi
On 2015-03-14, Ochal Christophe wrote:
> Dear Sir,
>
> On 03/14/2015 08:54 PM, Arend van Spriel wrote:
> > 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.
> >
> Okay.... Kind of wish I knew that a few hours ago before I formatted the
> thing :)
> I'll see if I can either reinstall Windows on it (somehow) or find
> someone with the same machine, I'm getting close to get pretty much
> everything running
You don't need to run windows for that, the nvram (calibration data,
probably the MAC address and related device specific data) is stored in
your mainboard's firmware - and exposed to userspace (under linux) via
/sys/firmware/efi/efivars/. You just need to identify the correct file
and copy it to a place where linux expects to find it
(/lib/firmware/brcm/brcmfmac43340-sdio.txt).
Regards
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2015-03-14 20:45 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 ` Broadcom 43340 Arend van Spriel
2015-03-14 20:07 ` Ochal Christophe
2015-03-14 20:39 ` Stefan Lippers-Hollmann [this message]
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=20150314213907.3f1167bb@mir \
--to=s.l-h@gmx.de \
--cc=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 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).