From: Arend van Spriel <arend@broadcom.com>
To: Bernd Wagener <Bernd.Wagener@Uni-Oldenburg.DE>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Linux Wireless <linux-wireless@vger.kernel.org>,
<frankyl@broadcom.com>
Subject: Re: brcmfmac NVRAM files
Date: Mon, 17 Feb 2014 18:38:40 +0100 [thread overview]
Message-ID: <53024920.8010104@broadcom.com> (raw)
In-Reply-To: <530248DD.1050408@broadcom.com>
On 02/17/14 18:37, Arend van Spriel wrote:
> On 02/17/14 17:52, Bernd Wagener wrote:
>> Am 17.02.2014 17:33, schrieb Samuel Ortiz:
>>> On Mon, Feb 17, 2014 at 04:06:40PM +0100, Samuel Ortiz wrote:
>>>> Hi Arend,
>>>>
>>>> I'm trying to use a 43241 SDIO chip here, and it fails asking for the
>>>> .txt file (brcmfmac43241b4-sdio.txt). This seems to be an NVRAM map
>>>> file, but I could not find either a template on linux-firmware or any
>>>> kind of documentation about it.
>>>>
>>>> How do distro handle that ? Are they expected to build their own, or is
>>>> it completely OEM pecific ?
>>> Adding Franky to the Cc list.
>>>
>>> Cheers,
>>> Samuel.
>>>
>> Hi Samuel,
>> I had the same proble with a wandboard here and I guess it's a bug. In
>> /lib/firmware/brcm are all reqired *.bin files, but no *.txt file. On
>> www.wandboard.or I found a SDK-Kit with brcmfmac4329-sdio.txt, copied
>> the file and then the wlan was running.
>> The *.txt are simply forgotten to copy to the firmware directory.
>> No idea how to fix this.
>
> Hi Bernd,
>
> The hint to solve this is found on wireless.kernel.org [1] and the
> answer is as Samuel suspects. This file is very board specific so OEMs
> manufacturing/selling the board should provide it either upon request or
> through some distribution like a SDK. Because of the nature of the file
> we do not put it on linux-firmware although people like yourself can get
> lucky trying ;-)
forgot:
[1] http://wireless.kernel.org/en/users/Drivers/brcm80211
> Regards,
> Arend
> --
> 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:[~2014-02-17 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:06 brcmfmac NVRAM files Samuel Ortiz
2014-02-17 16:33 ` Samuel Ortiz
2014-02-17 16:52 ` Bernd Wagener
2014-02-17 17:37 ` Arend van Spriel
2014-02-17 17:38 ` Arend van Spriel [this message]
2014-02-17 18:00 ` Samuel Ortiz
2014-02-17 18:27 ` Bernd Wagener
2014-02-18 9:58 ` Arend van Spriel
2014-03-05 2:31 ` Samuel Ortiz
2014-03-05 9:04 ` Arend van Spriel
2014-03-05 10:24 ` Samuel Ortiz
2014-03-05 16:15 ` Arend van Spriel
2014-03-05 16:50 ` Samuel Ortiz
2014-03-07 8:26 ` 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=53024920.8010104@broadcom.com \
--to=arend@broadcom.com \
--cc=Bernd.Wagener@Uni-Oldenburg.DE \
--cc=frankyl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.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 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).