From: Bernd Wagener <Bernd.Wagener@Uni-Oldenburg.DE>
To: Samuel Ortiz <sameo@linux.intel.com>,
Arend van Spriel <arend@broadcom.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>, frankyl@broadcom.com
Subject: Re: brcmfmac NVRAM files
Date: Mon, 17 Feb 2014 19:27:18 +0100 [thread overview]
Message-ID: <53025486.4040906@Uni-Oldenburg.DE> (raw)
In-Reply-To: <20140217180033.GM18868@zurbaran>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Am 17.02.2014 19:00, schrieb Samuel Ortiz:
> Hi Arend,
>
> On Mon, Feb 17, 2014 at 06:37:33PM +0100, Arend van Spriel wrote:
>> 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.
> There are several Win8 2-in-1 devices that do run the SDIO Full MAC
> chipsets and obviously there is no SDK for those. Which means no distro
> will ever be able to run out of the box on those.
> I may be completely off the mark here, but isn't there a sensible
> template for those guys ? Nothing optimised, but just something that
> would at least make things work...
>
> Also, the hint for pre 3.13 kernel is to copy the .bin into a .txt. Is
> that still the case for post 3.13 ?
>
> Cheers,
> Samuel.
>
No, thats wrong. You need a special board-specific *.txt file and rename
it for kernels > 3.12 to brcmfmacxxxx-sdio.txt.
Bernd
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3193 bytes --]
next prev parent reply other threads:[~2014-02-17 18:27 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
2014-02-17 18:00 ` Samuel Ortiz
2014-02-17 18:27 ` Bernd Wagener [this message]
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=53025486.4040906@Uni-Oldenburg.DE \
--to=bernd.wagener@uni-oldenburg.de \
--cc=arend@broadcom.com \
--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).