Status of Broadcom 4353?

Status of Broadcom 4353?

[Chen, Xianwen]

Hi there,

Thanks for keeping up good work on wireless support in Linux all these
years. I can still recall the joy when Realtek 8187 became part of
kernel supported driver a few years ago -- it actually was the main
reason I switched from NetBSD to Linux.

I now have a laptop from my employer, on which I sneaked Linux in. The
issue is that the wireless adapter seems not to be recognized:

lspci -vnn | grep 14e4
>> 02:00.0 Network controller [0280]: Broadcom Corporation Device [14e4:4353] (rev 01)

Though the new Broadcom driver seems to be more appropriate, I
actually compiled both the old and the new drivers. Further reading on
  http://linuxwireless.org/en/users/Drivers/brcm8021
and
  http://wireless.kernel.org/en/users/Drivers/b43
suggests that 4353 is not currently supported! :-(

What is the current status of Broadcom 4353? I'm curious and actually
eager to know. Any information will be appreciated!

Have a good day fellas!

Xianwen

Re: Status of Broadcom 4353?

[Larry Finger]

On 03/10/2011 12:37 PM, Chen, Xianwen wrote:
> Hi there,
>
> Thanks for keeping up good work on wireless support in Linux all these
> years. I can still recall the joy when Realtek 8187 became part of
> kernel supported driver a few years ago -- it actually was the main
> reason I switched from NetBSD to Linux.
>
> I now have a laptop from my employer, on which I sneaked Linux in. The
> issue is that the wireless adapter seems not to be recognized:
>
> lspci -vnn | grep 14e4
>>> 02:00.0 Network controller [0280]: Broadcom Corporation Device [14e4:4353] (rev 01)
>
> Though the new Broadcom driver seems to be more appropriate, I
> actually compiled both the old and the new drivers. Further reading on
>    http://linuxwireless.org/en/users/Drivers/brcm8021
> and
>    http://wireless.kernel.org/en/users/Drivers/b43
> suggests that 4353 is not currently supported! :-(
>
> What is the current status of Broadcom 4353? I'm curious and actually
> eager to know. Any information will be appreciated!
>
> Have a good day fellas!

There are two ways that Broadcom chips are connected to a PCIe interface - one 
uses the SSB interconnect, and the other does not. In b43, only chips with SSB 
are supported. As the 4353 device does not use SSB, b43 does not work with it. 
Whether it ever will is being discussed.

You should use either the brcm80211 driver from compat-wireless or kernels 
2.6.37, or later. You may also use the wl driver from Broadcom if you are 
willing to run closed-source software. That driver does not use mac80211.

Larry

RE: Status of Broadcom 4353?

[Brett Rudley]

SXRzIG5vdCBpbnR1aXRpdmUsIGJ1dCAweDQzNTMgaXMgdGhlIFBDSSBkZXZpY2UgSUQgb2YgdGhl
IDQzMjI0IGR1YWwgYmFuZCBjYXJkIHdoaWNoIGRvZXMgcnVuIHVuZGVyIGJyY204MDIxMS4gDQoN
ClJlZ2FyZHMNCkJyZXR0DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTog
bGludXgtd2lyZWxlc3Mtb3duZXJAdmdlci5rZXJuZWwub3JnIFttYWlsdG86bGludXgtd2lyZWxl
c3MtDQo+IG93bmVyQHZnZXIua2VybmVsLm9yZ10gT24gQmVoYWxmIE9mIENoZW4sIFhpYW53ZW4N
Cj4gU2VudDogVGh1cnNkYXksIE1hcmNoIDEwLCAyMDExIDEwOjM4IEFNDQo+IFRvOiBsaW51eC13
aXJlbGVzc0B2Z2VyLmtlcm5lbC5vcmcNCj4gU3ViamVjdDogU3RhdHVzIG9mIEJyb2FkY29tIDQz
NTM/DQo+IA0KPiBIaSB0aGVyZSwNCj4gDQo+IFRoYW5rcyBmb3Iga2VlcGluZyB1cCBnb29kIHdv
cmsgb24gd2lyZWxlc3Mgc3VwcG9ydCBpbiBMaW51eCBhbGwgdGhlc2UNCj4geWVhcnMuIEkgY2Fu
IHN0aWxsIHJlY2FsbCB0aGUgam95IHdoZW4gUmVhbHRlayA4MTg3IGJlY2FtZSBwYXJ0IG9mDQo+
IGtlcm5lbCBzdXBwb3J0ZWQgZHJpdmVyIGEgZmV3IHllYXJzIGFnbyAtLSBpdCBhY3R1YWxseSB3
YXMgdGhlIG1haW4NCj4gcmVhc29uIEkgc3dpdGNoZWQgZnJvbSBOZXRCU0QgdG8gTGludXguDQo+
IA0KPiBJIG5vdyBoYXZlIGEgbGFwdG9wIGZyb20gbXkgZW1wbG95ZXIsIG9uIHdoaWNoIEkgc25l
YWtlZCBMaW51eCBpbi4gVGhlDQo+IGlzc3VlIGlzIHRoYXQgdGhlIHdpcmVsZXNzIGFkYXB0ZXIg
c2VlbXMgbm90IHRvIGJlIHJlY29nbml6ZWQ6DQo+IA0KPiBsc3BjaSAtdm5uIHwgZ3JlcCAxNGU0
DQo+ID4+IDAyOjAwLjAgTmV0d29yayBjb250cm9sbGVyIFswMjgwXTogQnJvYWRjb20gQ29ycG9y
YXRpb24gRGV2aWNlDQo+IFsxNGU0OjQzNTNdIChyZXYgMDEpDQo+IA0KPiBUaG91Z2ggdGhlIG5l
dyBCcm9hZGNvbSBkcml2ZXIgc2VlbXMgdG8gYmUgbW9yZSBhcHByb3ByaWF0ZSwgSQ0KPiBhY3R1
YWxseSBjb21waWxlZCBib3RoIHRoZSBvbGQgYW5kIHRoZSBuZXcgZHJpdmVycy4gRnVydGhlciBy
ZWFkaW5nIG9uDQo+ICAgaHR0cDovL2xpbnV4d2lyZWxlc3Mub3JnL2VuL3VzZXJzL0RyaXZlcnMv
YnJjbTgwMjENCj4gYW5kDQo+ICAgaHR0cDovL3dpcmVsZXNzLmtlcm5lbC5vcmcvZW4vdXNlcnMv
RHJpdmVycy9iNDMNCj4gc3VnZ2VzdHMgdGhhdCA0MzUzIGlzIG5vdCBjdXJyZW50bHkgc3VwcG9y
dGVkISA6LSgNCj4gDQo+IFdoYXQgaXMgdGhlIGN1cnJlbnQgc3RhdHVzIG9mIEJyb2FkY29tIDQz
NTM/IEknbSBjdXJpb3VzIGFuZCBhY3R1YWxseQ0KPiBlYWdlciB0byBrbm93LiBBbnkgaW5mb3Jt
YXRpb24gd2lsbCBiZSBhcHByZWNpYXRlZCENCj4gDQo+IEhhdmUgYSBnb29kIGRheSBmZWxsYXMh
DQo+IA0KPiBYaWFud2VuDQo+IC0tDQo+IFRvIHVuc3Vic2NyaWJlIGZyb20gdGhpcyBsaXN0OiBz
ZW5kIHRoZSBsaW5lICJ1bnN1YnNjcmliZSBsaW51eC13aXJlbGVzcyINCj4gaW4NCj4gdGhlIGJv
ZHkgb2YgYSBtZXNzYWdlIHRvIG1ham9yZG9tb0B2Z2VyLmtlcm5lbC5vcmcNCj4gTW9yZSBtYWpv
cmRvbW8gaW5mbyBhdCAgaHR0cDovL3ZnZXIua2VybmVsLm9yZy9tYWpvcmRvbW8taW5mby5odG1s
DQoNCg==

Re: Status of Broadcom 4353?

[Chen, Xianwen]

Thanks a lot guys!

I tried both latest stable kernel (linux-2.6.37) and latest mainline
kernel (linux-2.6.38-rc8) with
  CONFIG_BRCM80211=y
  CONFIG_BRCM80211_PCI=y
. No wlan0 turns up yet.

Any more hint please?

Xianwen


On Thu, Mar 10, 2011 at 8:14 PM, Brett Rudley <brudley@broadcom.com> wrote:
> Its not intuitive, but 0x4353 is the PCI device ID of the 43224 dual band card which does run under brcm80211.
>
> Regards
> Brett


On Thu, Mar 10, 2011 at 7:54 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> There are two ways that Broadcom chips are connected to a PCIe interface -
> one uses the SSB interconnect, and the other does not. In b43, only chips
> with SSB are supported. As the 4353 device does not use SSB, b43 does not
> work with it. Whether it ever will is being discussed.
>
> You should use either the brcm80211 driver from compat-wireless or kernels
> 2.6.37, or later. You may also use the wl driver from Broadcom if you are
> willing to run closed-source software. That driver does not use mac80211.
>
> Larry

RE: Status of Broadcom 4353?

[Chaoxing Lin]

Is it possible that the firmware file your card needs is not in your Linux distribution? Upgrading kernel does not give you firmware file.

Usually, if this is the case, you may see some error log in "dmesg"

Just through a possibility, I don't have broadcom radios. But this scenario happened to me for my Intel "Ultimate N 6300"


-----Original Message-----
From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of Chen, Xianwen
Sent: Thursday, March 10, 2011 6:04 PM
To: linux-wireless@vger.kernel.org
Subject: Re: Status of Broadcom 4353?

Thanks a lot guys!

I tried both latest stable kernel (linux-2.6.37) and latest mainline
kernel (linux-2.6.38-rc8) with
  CONFIG_BRCM80211=y
  CONFIG_BRCM80211_PCI=y
. No wlan0 turns up yet.

Any more hint please?

Xianwen


On Thu, Mar 10, 2011 at 8:14 PM, Brett Rudley <brudley@broadcom.com> wrote:
> Its not intuitive, but 0x4353 is the PCI device ID of the 43224 dual band card which does run under brcm80211.
>
> Regards
> Brett


On Thu, Mar 10, 2011 at 7:54 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> There are two ways that Broadcom chips are connected to a PCIe interface -
> one uses the SSB interconnect, and the other does not. In b43, only chips
> with SSB are supported. As the 4353 device does not use SSB, b43 does not
> work with it. Whether it ever will is being discussed.
>
> You should use either the brcm80211 driver from compat-wireless or kernels
> 2.6.37, or later. You may also use the wl driver from Broadcom if you are
> willing to run closed-source software. That driver does not use mac80211.
>
> Larry
--
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

Re: Status of Broadcom 4353?

[Chen, Xianwen]

Thanks a lot guys!

I revisited http://linuxwireless.org/en/users/Drivers/brcm80211, but
did not find the firmware. Am I missing something?

Xianwen


On Fri, Mar 11, 2011 at 12:08 AM, Chaoxing Lin <CLin@3eti.com> wrote:
> Is it possible that the firmware file your card needs is not in your Linux distribution? Upgrading kernel does not give you firmware file.
>
> Usually, if this is the case, you may see some error log in "dmesg"
>
> Just through a possibility, I don't have broadcom radios. But this scenario happened to me for my Intel "Ultimate N 6300"
>

On Fri, Mar 11, 2011 at 3:26 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>
> Firmware?
>
>
>

Re: Status of Broadcom 4353?

[Larry Finger]

On 03/11/2011 09:05 AM, Chen, Xianwen wrote:
> Thanks a lot guys!
>
> I revisited http://linuxwireless.org/en/users/Drivers/brcm80211, but
> did not find the firmware. Am I missing something?

The firmware is in the linux-firmware tree. You probably need to install the 
latest package for your distro called "linux firmware" or "kernel firmware". 
Otherwise

git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git

The files you need will be in linux-firmware/brcm. Copy them to /lib/firmware/brcm.

Larry

Re: Status of Broadcom 4353?

[Rafał Miłecki]

2011/3/11 Larry Finger <Larry.Finger@lwfinger.net>:
> On 03/11/2011 09:05 AM, Chen, Xianwen wrote:
>>
>> Thanks a lot guys!
>>
>> I revisited http://linuxwireless.org/en/users/Drivers/brcm80211, but
>> did not find the firmware. Am I missing something?
>
> The firmware is in the linux-firmware tree. You probably need to install the
> latest package for your distro called "linux firmware" or "kernel firmware".
> Otherwise
>
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
>
> The files you need will be in linux-firmware/brcm. Copy them to
> /lib/firmware/brcm.

Or just use web gui :)

http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree;f=brcm;h=883e5732daa040c3c7d39b179c4b4b750db354cd;hb=HEAD

-- 
Rafał

Re: Status of Broadcom 4353?

[Chen, Xianwen]

Thanks a lot Chaoxing, Larry and Rafal,

I installed the Linux firmware (20110128), as you can see by 'ls
/lib/firmware/brcm/ -l'

  total 368
  -rw-r--r-- 1 root root 269595 Mar 11 16:57 bcm4329-fullmac-4-218-248-5.bin
  -rw-r--r-- 1 root root   1604 Mar 11 16:57 bcm4329-fullmac-4-218-248-5.txt
  -rw-r--r-- 1 root root  97376 Mar 11 16:57 bcm43xx-0-610-809-0.fw
  -rw-r--r-- 1 root root    180 Mar 11 16:57 bcm43xx_hdr-0-610-809-0.fw

However, after rebooting and even after recompiling and rebooting the
kernel, the wireless adapter doesn't yet show up.

Hence, I decide to give more details on the problem, to see if
something is missing:

(1) The Dell Latitude E5410 is running Gentoo AMD64 with all packages
up to date.

(2) The latest 2.6.38-rc8 kernel is used.

(3) The kernel config can be seen at http://pastebin.com/ExAzLHr8.

(4) The dmesg is uploaded to http://pastebin.com/wV3Wp54r.

(5) The output from lspci is at http://pastebin.com/Giqs7kkA.

Any thoughts, please?

Xianwen


2011/3/11 Rafał Miłecki <zajec5@gmail.com>:
> 2011/3/11 Larry Finger <Larry.Finger@lwfinger.net>:
>> On 03/11/2011 09:05 AM, Chen, Xianwen wrote:
>>>
>>> Thanks a lot guys!
>>>
>>> I revisited http://linuxwireless.org/en/users/Drivers/brcm80211, but
>>> did not find the firmware. Am I missing something?
>>
>> The firmware is in the linux-firmware tree. You probably need to install the
>> latest package for your distro called "linux firmware" or "kernel firmware".
>> Otherwise
>>
>> git clone
>> git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
>>
>> The files you need will be in linux-firmware/brcm. Copy them to
>> /lib/firmware/brcm.
>
> Or just use web gui :)
>
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree;f=brcm;h=883e5732daa040c3c7d39b179c4b4b750db354cd;hb=HEAD
>
> --
> Rafał
>

RE: Status of Broadcom 4353?

[Chaoxing Lin]

Try to put firmware in 
/lib/firmware/ instead of /lib/firmware/brcm/ which is the located in the git tree, but NOT necessarily the location the driver is looking for.


-----Original Message-----
From: Chen, Xianwen [mailto:xianwen.chen@gmail.com] 
Sent: Friday, March 11, 2011 11:43 AM
To: linux-wireless@vger.kernel.org
Cc: Larry Finger; Rafał Miłecki; Chaoxing Lin; Brett Rudley
Subject: Re: Status of Broadcom 4353?

Thanks a lot Chaoxing, Larry and Rafal,

I installed the Linux firmware (20110128), as you can see by 'ls
/lib/firmware/brcm/ -l'

  total 368
  -rw-r--r-- 1 root root 269595 Mar 11 16:57 bcm4329-fullmac-4-218-248-5.bin
  -rw-r--r-- 1 root root   1604 Mar 11 16:57 bcm4329-fullmac-4-218-248-5.txt
  -rw-r--r-- 1 root root  97376 Mar 11 16:57 bcm43xx-0-610-809-0.fw
  -rw-r--r-- 1 root root    180 Mar 11 16:57 bcm43xx_hdr-0-610-809-0.fw

However, after rebooting and even after recompiling and rebooting the
kernel, the wireless adapter doesn't yet show up.

Hence, I decide to give more details on the problem, to see if
something is missing:

(1) The Dell Latitude E5410 is running Gentoo AMD64 with all packages
up to date.

(2) The latest 2.6.38-rc8 kernel is used.

(3) The kernel config can be seen at http://pastebin.com/ExAzLHr8.

(4) The dmesg is uploaded to http://pastebin.com/wV3Wp54r.

(5) The output from lspci is at http://pastebin.com/Giqs7kkA.

Any thoughts, please?

Xianwen


2011/3/11 Rafał Miłecki <zajec5@gmail.com>:
> 2011/3/11 Larry Finger <Larry.Finger@lwfinger.net>:
>> On 03/11/2011 09:05 AM, Chen, Xianwen wrote:
>>>
>>> Thanks a lot guys!
>>>
>>> I revisited http://linuxwireless.org/en/users/Drivers/brcm80211, but
>>> did not find the firmware. Am I missing something?
>>
>> The firmware is in the linux-firmware tree. You probably need to install the
>> latest package for your distro called "linux firmware" or "kernel firmware".
>> Otherwise
>>
>> git clone
>> git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
>>
>> The files you need will be in linux-firmware/brcm. Copy them to
>> /lib/firmware/brcm.
>
> Or just use web gui :)
>
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree;f=brcm;h=883e5732daa040c3c7d39b179c4b4b750db354cd;hb=HEAD
>
> --
> Rafał
>

Re: Status of Broadcom 4353?

[Rafał Miłecki]

W dniu 11 marca 2011 17:58 użytkownik Chaoxing Lin <CLin@3eti.com> napisał:
> Try to put firmware in
> /lib/firmware/ instead of /lib/firmware/brcm/ which is the located in the git tree, but NOT necessarily the location the driver is looking for.

It is. Please, don't mess.

-- 
Rafał

RE: Status of Broadcom 4353?

[Chaoxing Lin]

Well, just throw some ideas. Not mean to mess.
Older Broadcom driver did put firmware in /lib/firmware/ e.g. BCM2033-FW.bin

-----Original Message-----
From: Rafał Miłecki [mailto:zajec5@gmail.com] 
Sent: Friday, March 11, 2011 12:02 PM
To: Chaoxing Lin
Cc: Chen, Xianwen; linux-wireless@vger.kernel.org; Larry Finger; Brett Rudley
Subject: Re: Status of Broadcom 4353?

W dniu 11 marca 2011 17:58 użytkownik Chaoxing Lin <CLin@3eti.com> napisał:
> Try to put firmware in
> /lib/firmware/ instead of /lib/firmware/brcm/ which is the located in the git tree, but NOT necessarily the location the driver is looking for.

It is. Please, don't mess.

-- 
Rafał

Re: Status of Broadcom 4353?

[Rafał Miłecki]

W dniu 11 marca 2011 18:21 użytkownik Chaoxing Lin <CLin@3eti.com> napisał:
> Well, just throw some ideas. Not mean to mess.
> Older Broadcom driver did put firmware in /lib/firmware/ e.g. BCM2033-FW.bin

I had no idea about that, sorry. Newest driver looks in brcm subdir,
I'm sure of that.

-- 
Rafał

Re: Status of Broadcom 4353?

[Rafał Miłecki]

2011/3/11 Chen, Xianwen <xianwen.chen@gmail.com>:
> Thanks a lot Chaoxing, Larry and Rafal,
>
> I installed the Linux firmware (20110128), as you can see by 'ls
> /lib/firmware/brcm/ -l'
>
>  total 368
>  -rw-r--r-- 1 root root 269595 Mar 11 16:57 bcm4329-fullmac-4-218-248-5.bin
>  -rw-r--r-- 1 root root   1604 Mar 11 16:57 bcm4329-fullmac-4-218-248-5.txt
>  -rw-r--r-- 1 root root  97376 Mar 11 16:57 bcm43xx-0-610-809-0.fw
>  -rw-r--r-- 1 root root    180 Mar 11 16:57 bcm43xx_hdr-0-610-809-0.fw
>
> However, after rebooting and even after recompiling and rebooting the
> kernel, the wireless adapter doesn't yet show up.
>
> Hence, I decide to give more details on the problem, to see if
> something is missing:
>
> (1) The Dell Latitude E5410 is running Gentoo AMD64 with all packages
> up to date.
>
> (2) The latest 2.6.38-rc8 kernel is used.
>
> (3) The kernel config can be seen at http://pastebin.com/ExAzLHr8.
>
> (4) The dmesg is uploaded to http://pastebin.com/wV3Wp54r.
>
> (5) The output from lspci is at http://pastebin.com/Giqs7kkA.
>
> Any thoughts, please?

1) Update your pci db (sudo update-pciids)
2) Reboot maybe? I don't know if this is needed for lspci
3) Give us lspci -nn
4) Give us "lsmod | grep brcm80211"
5) Execute: "sudo modprobe brcm80211"
6) Give us "dmesg | grep brcm80211"

-- 
Rafał

Re: Status of Broadcom 4353?

[Henry Ptasinski]

VHJ5Og0KDQpsbiAtcyBiY200M3h4LTAtNjEwLTgwOS0wLmZ3IGJjbTQzeHgtLTAuZncNCmxuIC1z
IGJjbTQzeHhfaGRyLTAtNjEwLTgwOS0wLmZ3IGJjbTQzeHhfaGRyLTAuZncNCg0KKE9yIGp1c3Qg
cmVuYW1lIHRoZSBmaWxlcykuDQoNCldlIGRyb3BwZWQgdGhlIHJlbGVhc2UgbnVtYmVycyBmcm9t
IHRoZSBmaWxlbmFtZXMgYSB3aGlsZSBhZ28uIEkgc2VudCBhIHBhdGNoIHRvIHJlbmFtZSB0aGUg
ZmlsZXMgaW4gdGhlIHJlcG8sIGJ1dCBJIGRvbid0IHRoaW5rIGl0IGV2ZXIgZ290IGFwcGxpZWQu
DQoNCi0gSGVucnkNCg0KSGVucnkgUHRhc2luc2tpDQpoZW5yeXBAYnJvYWRjb20uY29tDQoNCi0t
LS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206IGxpbnV4LXdpcmVsZXNzLW93bmVyQHZn
ZXIua2VybmVsLm9yZyA8bGludXgtd2lyZWxlc3Mtb3duZXJAdmdlci5rZXJuZWwub3JnPg0KVG86
IGxpbnV4LXdpcmVsZXNzQHZnZXIua2VybmVsLm9yZyA8bGludXgtd2lyZWxlc3NAdmdlci5rZXJu
ZWwub3JnPg0KQ2M6IExhcnJ5IEZpbmdlciA8TGFycnkuRmluZ2VyQGx3ZmluZ2VyLm5ldD47IFJh
ZmHFgiBNacWCZWNraSA8emFqZWM1QGdtYWlsLmNvbT47IENoYW94aW5nIExpbiA8Q0xpbkAzZXRp
LmNvbT47IEJyZXR0IFJ1ZGxleQ0KU2VudDogRnJpIE1hciAxMSAwODo0MzoyNCAyMDExClN1Ympl
Y3Q6IFJlOiBTdGF0dXMgb2YgQnJvYWRjb20gNDM1Mz8NCg0KVGhhbmtzIGEgbG90IENoYW94aW5n
LCBMYXJyeSBhbmQgUmFmYWwsDQoNCkkgaW5zdGFsbGVkIHRoZSBMaW51eCBmaXJtd2FyZSAoMjAx
MTAxMjgpLCBhcyB5b3UgY2FuIHNlZSBieSAnbHMNCi9saWIvZmlybXdhcmUvYnJjbS8gLWwnDQoN
CiAgdG90YWwgMzY4DQogIC1ydy1yLS1yLS0gMSByb290IHJvb3QgMjY5NTk1IE1hciAxMSAxNjo1
NyBiY200MzI5LWZ1bGxtYWMtNC0yMTgtMjQ4LTUuYmluDQogIC1ydy1yLS1yLS0gMSByb290IHJv
b3QgICAxNjA0IE1hciAxMSAxNjo1NyBiY200MzI5LWZ1bGxtYWMtNC0yMTgtMjQ4LTUudHh0DQog
IC1ydy1yLS1yLS0gMSByb290IHJvb3QgIDk3Mzc2IE1hciAxMSAxNjo1NyBiY200M3h4LTAtNjEw
LTgwOS0wLmZ3DQogIC1ydy1yLS1yLS0gMSByb290IHJvb3QgICAgMTgwIE1hciAxMSAxNjo1NyBi
Y200M3h4X2hkci0wLTYxMC04MDktMC5mdw0KDQpIb3dldmVyLCBhZnRlciByZWJvb3RpbmcgYW5k
IGV2ZW4gYWZ0ZXIgcmVjb21waWxpbmcgYW5kIHJlYm9vdGluZyB0aGUNCmtlcm5lbCwgdGhlIHdp
cmVsZXNzIGFkYXB0ZXIgZG9lc24ndCB5ZXQgc2hvdyB1cC4NCg0KSGVuY2UsIEkgZGVjaWRlIHRv
IGdpdmUgbW9yZSBkZXRhaWxzIG9uIHRoZSBwcm9ibGVtLCB0byBzZWUgaWYNCnNvbWV0aGluZyBp
cyBtaXNzaW5nOg0KDQooMSkgVGhlIERlbGwgTGF0aXR1ZGUgRTU0MTAgaXMgcnVubmluZyBHZW50
b28gQU1ENjQgd2l0aCBhbGwgcGFja2FnZXMNCnVwIHRvIGRhdGUuDQoNCigyKSBUaGUgbGF0ZXN0
IDIuNi4zOC1yYzgga2VybmVsIGlzIHVzZWQuDQoNCigzKSBUaGUga2VybmVsIGNvbmZpZyBjYW4g
YmUgc2VlbiBhdCBodHRwOi8vcGFzdGViaW4uY29tL0V4QXpMSHI4Lg0KDQooNCkgVGhlIGRtZXNn
IGlzIHVwbG9hZGVkIHRvIGh0dHA6Ly9wYXN0ZWJpbi5jb20vd1YzV3A1NHIuDQoNCig1KSBUaGUg
b3V0cHV0IGZyb20gbHNwY2kgaXMgYXQgaHR0cDovL3Bhc3RlYmluLmNvbS9HaXFzN2trQS4NCg0K
QW55IHRob3VnaHRzLCBwbGVhc2U/DQoNClhpYW53ZW4NCg0KDQoyMDExLzMvMTEgUmFmYcWCIE1p
xYJlY2tpIDx6YWplYzVAZ21haWwuY29tPjoNCj4gMjAxMS8zLzExIExhcnJ5IEZpbmdlciA8TGFy
cnkuRmluZ2VyQGx3ZmluZ2VyLm5ldD46DQo+PiBPbiAwMy8xMS8yMDExIDA5OjA1IEFNLCBDaGVu
LCBYaWFud2VuIHdyb3RlOg0KPj4+DQo+Pj4gVGhhbmtzIGEgbG90IGd1eXMhDQo+Pj4NCj4+PiBJ
IHJldmlzaXRlZCBodHRwOi8vbGludXh3aXJlbGVzcy5vcmcvZW4vdXNlcnMvRHJpdmVycy9icmNt
ODAyMTEsIGJ1dA0KPj4+IGRpZCBub3QgZmluZCB0aGUgZmlybXdhcmUuIEFtIEkgbWlzc2luZyBz
b21ldGhpbmc/DQo+Pg0KPj4gVGhlIGZpcm13YXJlIGlzIGluIHRoZSBsaW51eC1maXJtd2FyZSB0
cmVlLiBZb3UgcHJvYmFibHkgbmVlZCB0byBpbnN0YWxsIHRoZQ0KPj4gbGF0ZXN0IHBhY2thZ2Ug
Zm9yIHlvdXIgZGlzdHJvIGNhbGxlZCAibGludXggZmlybXdhcmUiIG9yICJrZXJuZWwgZmlybXdh
cmUiLg0KPj4gT3RoZXJ3aXNlDQo+Pg0KPj4gZ2l0IGNsb25lDQo+PiBnaXQ6Ly9naXQua2VybmVs
Lm9yZy9wdWIvc2NtL2xpbnV4L2tlcm5lbC9naXQvZHdtdzIvbGludXgtZmlybXdhcmUuZ2l0DQo+
Pg0KPj4gVGhlIGZpbGVzIHlvdSBuZWVkIHdpbGwgYmUgaW4gbGludXgtZmlybXdhcmUvYnJjbS4g
Q29weSB0aGVtIHRvDQo+PiAvbGliL2Zpcm13YXJlL2JyY20uDQo+DQo+IE9yIGp1c3QgdXNlIHdl
YiBndWkgOikNCj4NCj4gaHR0cDovL2dpdC5rZXJuZWwub3JnLz9wPWxpbnV4L2tlcm5lbC9naXQv
ZHdtdzIvbGludXgtZmlybXdhcmUuZ2l0O2E9dHJlZTtmPWJyY207aD04ODNlNTczMmRhYTA0MGMz
YzdkMzliMTc5YzRiNGI3NTBkYjM1NGNkO2hiPUhFQUQNCj4NCj4gLS0NCj4gUmFmYcWCDQo+DQot
LQ0KVG8gdW5zdWJzY3JpYmUgZnJvbSB0aGlzIGxpc3Q6IHNlbmQgdGhlIGxpbmUgInVuc3Vic2Ny
aWJlIGxpbnV4LXdpcmVsZXNzIiBpbg0KdGhlIGJvZHkgb2YgYSBtZXNzYWdlIHRvIG1ham9yZG9t
b0B2Z2VyLmtlcm5lbC5vcmcNCk1vcmUgbWFqb3Jkb21vIGluZm8gYXQgIGh0dHA6Ly92Z2VyLmtl
cm5lbC5vcmcvbWFqb3Jkb21vLWluZm8uaHRtbA0KDQo=

Re: Status of Broadcom 4353?

[Chen, Xianwen]

Hi guys,

Thanks a lot to all of you! wlan1 showed up after renaming the two files. :D

Henry, there is a typo that it needs to "be bcm43xx-0.fw", not
"bcm43xx--0.fw". Thanks!

Rafal, "dmesg | grep "brcm80211"" really helped locating the issue!
BTW, rebooting is not required after updating PCI information
database. Thanks!

Chaoxing, thanks for the efforts! I really appreciate them too!

Have a nice weekend fellas! ;p

Xianwen

On Fri, Mar 11, 2011 at 6:10 PM, Henry Ptasinski <henryp@broadcom.com> wrote:
> Try:
>
> ln -s bcm43xx-0-610-809-0.fw bcm43xx--0.fw
> ln -s bcm43xx_hdr-0-610-809-0.fw bcm43xx_hdr-0.fw
>
> (Or just rename the files).
>
> We dropped the release numbers from the filenames a while ago. I sent a patch to rename the files in the repo, but I don't think it ever got applied.
>
> - Henry
>
> Henry Ptasinski
> henryp@broadcom.com
>

Re: Status of Broadcom 4353?

[Henry Ptasinski]

Pj4gV2VsbCwganVzdCB0aHJvdyBzb21lIGlkZWFzLiBOb3QgbWVhbiB0byBtZXNzLg0KPj4gT2xk
ZXIgQnJvYWRjb20gZHJpdmVyIGRpZCBwdXQgZmlybXdhcmUgaW4gL2xpYi8+PmZpcm13YXJlLyBl
LmcuIEJDTTIwMzMtRlcuYmluDQo+DQo+SSBoYWQgbm8gaWRlYSBhYm91dCB0aGF0LCBzb3JyeS4g
TmV3ZXN0IGRyaXZlciBsb29rcyA+aW4gYnJjbSBzdWJkaXIsDQo+SSdtIHN1cmUgb2YgdGhhdC4N
Cg0KWWVzLCB0aGUgd2xhbiBkcml2ZXJzIChicmNtc21hYywgYnJjbWZtYWMpIGxvb2sgaW4gdGhl
IGJyY20gc3ViZGlyLg0KDQotIEhlbnJ5DQoNCkhlbnJ5IFB0YXNpbnNraQ0KaGVucnlwQGJyb2Fk
Y29tLmNvbQ==