From: Arend van Spriel <arend@broadcom.com>
To: Ben Adler <ben@phoenix-aerial.com>
Cc: brcm80211 development <brcm80211-dev-list@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4330 linux support
Date: Fri, 6 Feb 2015 10:10:55 +0100 [thread overview]
Message-ID: <54D4851F.8020402@broadcom.com> (raw)
In-Reply-To: <54D3FF89.502@phoenix-aerial.com>
+ lists
On 02/06/15 00:40, Ben Adler wrote:
> Hi Arend,
>
> I found your email on
> https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211 and would
> like to ask your help regarding linux support for the Broadcom BCM4330
> chipset. The page lists it as supported.
>
> More precisely, I am trying to get WiFi to work on a Zotac ZBOX pico 320
> which contains an Ampak AP6383 chip. This in turn contains a BCM4330...
> which leads me to you.
Makes sense ;-)
> So far, I was able to rip
>
> 4330b2rtecdc.bin (md5 ca91920df0041bd9e31e3aef53ac3375)
> T77H360.04_WB_nvram_20120731.txt (attached)
>
> out of the windows driver and am able to scan for networks using linux
> 3.19rc6, brcmfmac module and "iwlist wlan0 scanning". However, doing so,
> I receive many error messages and cannot connect to an AP, let alone
> start an AP with hostapd.
>
> The firmware files in linux-firmware, don't seem to help either.
>
> Arend, is it possible to make this chip work? Just STA, or also AP? If
> so, which firmware and NVRAM files will I need?
Well, I have this chip running on regular x86 laptop using special
adapter boards and it also runs on i.MX6 board. The windows firmware and
nvram should work. Can you send a kernel log preferably with driver
module loaded with 'debug=0xd416'.
> The windows driver also contains 11
> BCM4330B1_002.001.003.0967.<XXXX>.hcd files. Are those only for
> bluetooth? Does bluetooth work in linux?
Those .hcd file are indeed for bluetooth. I know next to nothing about
bluetooth. Sorry.
> Thanks for your time!
> Ben
Regards,
Arend
next parent reply other threads:[~2015-02-06 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54D3FF89.502@phoenix-aerial.com>
2015-02-06 9:10 ` Arend van Spriel [this message]
2015-02-06 14:45 ` BCM4330 linux support Ben Adler
2015-02-06 16:00 ` Arend van Spriel
2015-02-07 1:53 ` Benjamin Adler
2015-02-07 18:12 ` Arend van Spriel
2015-02-07 19:14 ` Benjamin Adler
2015-02-07 19:37 ` Arend van Spriel
2015-02-07 22:20 ` Benjamin Adler
2015-02-06 16:06 ` 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=54D4851F.8020402@broadcom.com \
--to=arend@broadcom.com \
--cc=ben@phoenix-aerial.com \
--cc=brcm80211-dev-list@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).