From: Dan Williams <dcbw@redhat.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de,
Larry Finger <Larry.Finger@lwfinger.net>,
Francesco Gringoli <francesco.gringoli@ing.unibs.it>,
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 13:50:37 -0500 [thread overview]
Message-ID: <1232736637.2577.40.camel@localhost.localdomain> (raw)
In-Reply-To: <200901231908.05835.mb@bu3sch.de>
On Fri, 2009-01-23 at 19:08 +0100, Michael Buesch wrote:
> On Friday 23 January 2009 19:01:00 Larry Finger wrote:
> > 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.
>
> I already posted that, but in case you missed it:
> http://bu3sch.de/patches/wireless-testing/20081227-1821/patches/008-b43-probe-open-fw.patch
Preferring the proprietary firmware over the open firmware (for now)
seems like the best approach at this time. Many people will be quite
happy with the open firmware that we can actually ship in distros, and
those that aren't can do the fwcutter stuff and get their own
proprietary firmware. If for some reason the open firmware isn't
working, use fwcutter and get the proprietary firmware, which you would
have had to do before anyway. And those people with chips that aren't
supported by the proprietary firmware yet still have to use the
fwcutter, which they would have had to do anyway. Win all around.
If in the future there's a set of chips that the open firmware is known
to work exceptionally well on, it could be preferred over the
proprietary firmware at that point.
Dan
next prev parent reply other threads:[~2009-01-23 18:52 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 [this message]
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=1232736637.2577.40.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--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=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).