From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Arend van Spriel <arend@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmsmac and BCM47186 (BCM5357) + brcmfmac and BCM43236 V2
Date: Sun, 29 Jul 2012 17:25:23 +0200 [thread overview]
Message-ID: <501555E3.8080304@hauke-m.de> (raw)
In-Reply-To: <CACna6rzO2579YdN_GdmP+=-+L308KjKhKsejevAzJ19dp6LxVg@mail.gmail.com>
On 07/29/2012 01:34 PM, Rafał Miłecki wrote:
> 2012/5/18 Hauke Mehrtens <hauke@hauke-m.de>:
>> I got a new device, a Linksys E3200 with a BCM47186 (id: 0x5357) and a
>> BCM43236 v2 for 5GHz wifi.
>>
>> The BCM47186 has a wifi core rev 28, a N-PHY rev 9 and a 2057 radio rev
>> 5 and it does not work with brcmsmac or b43. :-(
>>
>> Are there plans to add support for such new N-PHY revs to brcmsmac and
>> the firmware?
>>
>> Here are some parts of my log with brcmsamc with firmware from
>> linux-firmware.
>>
>> bcma: Found chip with id 0x5357, rev 0x02 and package 0x0A
>> ....
>> bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x1C, class 0x0)
>> ....
>> [ 14.776000] b43-phy0: Broadcom 5357 WLAN found (core revision 28)
>> [ 14.780000] b43-phy0 debug: Found PHY: Analog 9, Type 4, Revision 9
>
> Hauke, is this 0x5357 a SoC bcma, or additional bcma connected via
> PCIE to the main one? If it's the second case, could you provide pci
> id, please?
>
Hi Rafał,
0x5357 is a SoC with a ieee80211 core, but no PCIe core, just USB 2.0.
Should I add all the SoC chips I know of to the b43 device list?
Hauke
prev parent reply other threads:[~2012-07-29 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 22:32 brcmsmac and BCM47186 (BCM5357) + brcmfmac and BCM43236 V2 Hauke Mehrtens
2012-05-25 20:32 ` Arend van Spriel
2012-07-29 11:34 ` Rafał Miłecki
2012-07-29 15:25 ` Hauke Mehrtens [this message]
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=501555E3.8080304@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--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).