From: Michael Buesch <mb@bu3sch.de>
To: Francesco Gringoli <francesco.gringoli@ing.unibs.it>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
"John W. Linville" <linville@tuxdriver.com>,
bcm43xx-dev@lists.berlios.de,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: integration of opensource firmware with b43 kernel driver
Date: Fri, 23 Jan 2009 20:37:42 +0100 [thread overview]
Message-ID: <200901232037.42512.mb@bu3sch.de> (raw)
In-Reply-To: <01F0FEC9-8ECF-4284-9428-701B976286D6@ing.unibs.it>
On Friday 23 January 2009 20:24:47 Francesco Gringoli wrote:
> On Jan 23, 2009, at 7:01 PM, Larry Finger wrote:
>
> > Francesco Gringoli wrote:
> >> Hello,
> >>
> >> we have been testing the firmware for a week now and it seems
> >> stable. I
> >> personally tested it also on a Linksys WRT54GL and it works both in
> >> station and in AP modes. I collected the feedbacks that some of you
> >> sent
> >> and it seems that the firmware now runs on these board:
> >>
> >> - 4306, 4311, 4318, 4320
> >
> > As a point of clarification, I think this is restricted to the 4311/1
> > as the 4311/2 uses ucode13, not ucode5. If you need a tester for an
> > open-source version of the 13 firmware, I'm available.
> Damn... that would be a very hard writing.... We do not have any
> 4311/2 board: at first glance there are more condition registers whose
> meaning we do not know. Very different hardware, didn't know. Thank
> you for the feedback.
Well, if you didn't notice it already, there are a zillion different flavors
of the broadcom wireless chip out there. So if you buy a random device, you're almost
guaranteed that you don't have that flavor already. ;)
Another thing is: You simply can _not_ distinguish the devices by the 43xx number in practice.
There are too many devices with the same 43xx number, but different internal designs.
The safest solution for the firmware is to tell by the wireless core revision whether it works or not.
(However, that still leaves a few traps for different PHY and radio revisions, as the firmware also
accesses PHY and radio).
--
Greetings, Michael.
next prev parent reply other threads:[~2009-01-23 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 17:36 integration of opensource firmware with b43 kernel driver Francesco Gringoli
2009-01-23 17:44 ` Brian J. Murrell
2009-01-23 19:58 ` Francesco Gringoli
2009-01-23 18:01 ` Larry Finger
2009-01-23 18:08 ` Michael Buesch
2009-01-23 18:50 ` Dan Williams
2009-01-23 19:05 ` Michael Buesch
2009-01-23 19:24 ` Francesco Gringoli
2009-01-23 19:37 ` Michael Buesch [this message]
2009-01-23 19:51 ` Francesco Gringoli
2009-01-23 19:45 ` Larry Finger
2009-01-23 18:02 ` Michael Buesch
2009-01-23 19:18 ` Francesco Gringoli
2009-01-23 19:33 ` Michael Buesch
2009-01-23 19:46 ` Francesco Gringoli
2009-01-23 19:50 ` Michael Buesch
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=200901232037.42512.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=francesco.gringoli@ing.unibs.it \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).