From: Michael Buesch <mb@bu3sch.de>
To: Francesco Gringoli <francesco.gringoli@ing.unibs.it>
Cc: bcm43xx-dev@lists.berlios.de,
"John W. Linville" <linville@tuxdriver.com>,
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:50:27 +0100 [thread overview]
Message-ID: <200901232050.27952.mb@bu3sch.de> (raw)
In-Reply-To: <FE3E070D-F92B-4A76-80E5-019D4735FBED@ing.unibs.it>
On Friday 23 January 2009 20:46:45 Francesco Gringoli wrote:
> -- Is using the Broadcom names for the firmware the best course of
> -- action? What if the opensource firmware files were named something
> -- like "os-ucode5.fw", etc. and b43 were coded to check for those files
> -- first? It would then fall back to the standard firmware if the
> -- opensource version is not found.
I answered to this question with this patch:
http://bu3sch.de/patches/wireless-testing/20081227-1821/patches/008-b43-probe-open-fw.patch
I am currently testing an updated version of the patch and I'll push it upstream tomorrow.
--
Greetings, Michael.
prev parent reply other threads:[~2009-01-23 19:51 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
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 [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=200901232050.27952.mb@bu3sch.de \
--to=mb@bu3sch.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.