From: "Chen, Xianwen" <xianwen.chen@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Larry Finger <Larry.Finger@lwfinger.net>, Chaoxing Lin <CLin@3eti.com>
Subject: Re: Status of Broadcom 4353?
Date: Fri, 11 Mar 2011 16:05:28 +0100 [thread overview]
Message-ID: <AANLkTim3c200SL3icCMV7VGcyEaBQ3d6b19vSOerThib@mail.gmail.com> (raw)
In-Reply-To: <4D798863.2060303@lwfinger.net>
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?
>
>
>
next prev parent reply other threads:[~2011-03-11 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 18:37 Status of Broadcom 4353? Chen, Xianwen
2011-03-10 18:54 ` Larry Finger
2011-03-10 19:14 ` Brett Rudley
2011-03-10 23:03 ` Chen, Xianwen
2011-03-10 23:08 ` Chaoxing Lin
[not found] ` <4D798863.2060303@lwfinger.net>
2011-03-11 15:05 ` Chen, Xianwen [this message]
2011-03-11 15:24 ` Larry Finger
2011-03-11 16:16 ` Rafał Miłecki
2011-03-11 16:43 ` Chen, Xianwen
2011-03-11 16:58 ` Chaoxing Lin
2011-03-11 17:01 ` Rafał Miłecki
2011-03-11 17:21 ` Chaoxing Lin
2011-03-11 17:27 ` Rafał Miłecki
2011-03-11 17:00 ` Rafał Miłecki
-- strict thread matches above, loose matches on Subject: below --
2011-03-11 17:10 Henry Ptasinski
2011-03-11 17:55 ` Chen, Xianwen
2011-03-11 17:35 Henry Ptasinski
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=AANLkTim3c200SL3icCMV7VGcyEaBQ3d6b19vSOerThib@mail.gmail.com \
--to=xianwen.chen@gmail.com \
--cc=CLin@3eti.com \
--cc=Larry.Finger@lwfinger.net \
--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