From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linville@tuxdriver.com, bcm43xx-dev@lists.berlios.de,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Automatically probe for opensource firmware
Date: Sat, 24 Jan 2009 06:58:35 +0100 [thread overview]
Message-ID: <200901240658.35490.mb@bu3sch.de> (raw)
In-Reply-To: <497AA16F.30409@lwfinger.net>
On Saturday 24 January 2009 06:04:47 Larry Finger wrote:
> Michael Buesch wrote:
> > First probe for proprietary firmware and then probe for opensource firmware.
> > This way around it's a win-win situation.
> > 1) If proprietary fw is available, it will work.
> > 2) If opensource firmware is available, but no proprietary (Distros can only ship open fw)
> > it might work.
> > 3) If both open and proprietary are available, it will work, because it selects
> > the proprietary. We currently don't prefer the open fw in this case, because it doesn't
> > work on all devices. It would introduce a regression otherwise.
> >
> > The remaining FIXMEs in this patch are harmless, because they only matter on multiband
> > devices, which are not implemented yet anyway.
> >
> > Signed-off-by: Michael Buesch <mb@bu3sch.de>
> >
> > ---
> >
> > John, please queue for the next feature round.
>
> Acked-by: Larry Finger <Larry.Finger@lwfinger.net>
>
> I made one temporary change to search for open-source firmware before
> the proprietary version because I boot kernels that are not changed to
> handle the o-s version, but still want to test when I can.
>
> I understand and approve of your logic - it just doesn't fit my
> current agenda.
You can still use the fwpostfix module parameter, of course.
--
Greetings, Michael.
prev parent reply other threads:[~2009-01-24 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 20:21 [PATCH] b43: Automatically probe for opensource firmware Michael Buesch
2009-01-24 5:04 ` Larry Finger
2009-01-24 5:58 ` 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=200901240658.35490.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--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).