From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Naughtboy <skylvlinux@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: bcm43236 complient in the compat-wireless-3.6.81???
Date: Fri, 20 Dec 2013 13:24:56 +0100 [thread overview]
Message-ID: <52B43718.504@broadcom.com> (raw)
In-Reply-To: <CACna6rwU8hroahpVsM7KTJD1iM2=12JuErr5LgCvswx+XsTjjA@mail.gmail.com>
On 12/20/2013 08:57 AM, Rafał Miłecki wrote:
> 2013/12/19 Arend van Spriel <arend@broadcom.com>:
>> It is in the kernel tree under
>> 'drivers/net/wireless/brcm80211/brcmfmac'. We only support rev 3 because
>> rev 2 and earlier do not have enough memory to run fullmac firmware.
>> However, I have not found any rev 3 on the market. If you have please
>> let me know.
>
> Could you say something more about rev 2? How does it work with
> internal Broadcom driver? Is the firmware stored somewhere else? Does
> it have some another kind of memory?
It has a split-mac design. So at one end the spectrum there is
mac80211-type drivers and at the other side are fullmac drivers like
brcmfmac. rev 2 driver sits right in the middle of that with part of the
802.11 stack running on the host and part on the device. This device has
not enough memory to run the fullmac firmware.
Gr. AvS
> Apart from the firmware storing issue, is the communication between
> driver and hardware the same?
> --
> 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:[~2013-12-20 12:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 10:03 bcm43236 complient in the compat-wireless-3.6.81??? Naughtboy
2013-12-19 12:27 ` Hauke Mehrtens
[not found] ` <CAKH5=LsaEw7GEHs5nb1omDeSMmcoFSXo8EEy+DeXvyXF5_1M_g@mail.gmail.com>
2013-12-19 14:21 ` Hauke Mehrtens
2013-12-19 15:41 ` Arend van Spriel
2013-12-20 7:57 ` Rafał Miłecki
2013-12-20 12:24 ` Arend van Spriel [this message]
2014-01-12 14:17 ` Rafał Miłecki
2014-01-12 14:33 ` Arend van Spriel
2014-01-12 20:13 ` Rafał Miłecki
2014-01-13 16:18 ` Arend van Spriel
[not found] ` <CAKH5=LvUqfyqW5NQGNzCec2yVrzFqFWCbtQvF5ZL=cjkh=9HOw@mail.gmail.com>
2013-12-20 9:30 ` 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=52B43718.504@broadcom.com \
--to=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=skylvlinux@gmail.com \
--cc=zajec5@gmail.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).