From: Samuel Ortiz <sameo@linux.intel.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Bernd Wagener <Bernd.Wagener@Uni-Oldenburg.DE>,
Linux Wireless <linux-wireless@vger.kernel.org>,
frankyl@broadcom.com
Subject: Re: brcmfmac NVRAM files
Date: Mon, 17 Feb 2014 19:00:33 +0100 [thread overview]
Message-ID: <20140217180033.GM18868@zurbaran> (raw)
In-Reply-To: <530248DD.1050408@broadcom.com>
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.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2014-02-17 18:00 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 [this message]
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=20140217180033.GM18868@zurbaran \
--to=sameo@linux.intel.com \
--cc=Bernd.Wagener@Uni-Oldenburg.DE \
--cc=arend@broadcom.com \
--cc=frankyl@broadcom.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).