From: Arend van Spriel <arend@broadcom.com>
To: "Jürgen Bausa" <juergen.Bausa@online.de>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: Broadcom 43340
Date: Sun, 15 Mar 2015 22:14:57 +0100 [thread overview]
Message-ID: <5505F651.3060607@broadcom.com> (raw)
In-Reply-To: <loom.20150315T213441-211@post.gmane.org>
On 03/15/15 21:38, Jürgen Bausa wrote:
> Arend van Spriel<arend@...> writes:
>
>>
>> On 03/14/15 23:13, Ochal Christophe wrote:
>>> All,
>>>
>>> On 03/14/2015 09:39 PM, Stefan Lippers-Hollmann wrote:
>>>> 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
>>>
>>> Thanks for the hint, that did it, I'm online!
>>
>> Apparently my hint was not clear enough. Good to hear it works for you.
>>
>
> Dear Arend,
>
> would be nice, if you could make it clear.
>
> I am in the exact some position (asus x205 with linux 4.0 rc3) but my
> /sys/firmware/efi/efivars/ is empty. I am running debian jessie with a
> kernel taken from ubuntu. Am I missing something? Even loading efivars via
> modprobe doesnt change a thing.
Maybe you need to mount it. This is what I found [1]:
$ sudo mount -t efivarfs none /sys/firmware/efi/efivars
Regards,
Arend
[1] http://firmware.intel.com/blog/accessing-uefi-variables-linux
> Juergen
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-15 21:15 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
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 [this message]
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=5505F651.3060607@broadcom.com \
--to=arend@broadcom.com \
--cc=juergen.Bausa@online.de \
--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).