From: Larry Finger <Larry.Finger@lwfinger.net>
To: Francesco Gringoli <francesco.gringoli@ing.unibs.it>
Cc: Michael Buesch <mb@bu3sch.de>,
"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 12:01:00 -0600 [thread overview]
Message-ID: <497A05DC.4040101@lwfinger.net> (raw)
In-Reply-To: <FF33C500-6653-4A69-B34D-FBE47B2136D3@ing.unibs.it>
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.
> I was considering the suggestions you all gave me a few days ago and
> other questions related to the possible integration of this firmware
> into the kernel, and I came to these conclusions/questions (please
> forgive me for this long message :-) )
>
> - change the name of the initvals for the opensource firmware: this
> seems a little bit complicated as now the decision about the
> initval-files' names and the detection of the firmware type are
> respectively based on the phy type and on the firmware date. This means
> that initval-files' names can be determine as soon as the hardware type
> has been probed, while the firmware needs to be started before the
> kernel can determine if it is opensource or not: at this time, however,
> the initvals have already been uploaded. What can we do?
The driver can certainly be coded to look for the open-source firmware
names before trying to load vendor firmware. That way there will not
be any confusion.
> - detection of the opensource firmware capabilities: are you really sure
> we cannot use a shm location that the bcm proprietary firmware uses for
> some other purpose? Once, in fact, the kernel has determined that the
> firmware is opensource it can also use a given location in a different
> manner than it would do for a proprietary firmware. However this is not
> a problem at all :-) as we can use one location in the "high" shm-memory
> area, let's say > 0xb00, just choose one.
I think it best to choose an unused location.
Larry
next prev parent reply other threads:[~2009-01-23 18:01 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 [this message]
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
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=497A05DC.4040101@lwfinger.net \
--to=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 \
--cc=mb@bu3sch.de \
/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).