From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: bcm43xx-dev@lists.berlios.de,
Johannes Berg <johannes@sipsolutions.net>,
kyle@infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [b43] opensource firmware
Date: Thu, 15 Jan 2009 17:09:49 +0100 [thread overview]
Message-ID: <200901151709.49811.mb@bu3sch.de> (raw)
In-Reply-To: <496F5D4F.3020805@lwfinger.net>
On Thursday 15 January 2009 16:59:11 Larry Finger wrote:
> Michael Buesch wrote:
> > Yes, please introduce a feature-bitfield at some location in SHM that's unused
> > by the proprietary firmware. This bitfields would contain a bit for QoS and
> > a bit for hwcrypto.
> > Also change your firmware so the driver detects it as open-source firmware.
> > I think that's done by writing 0xFFFF to the date/time field in SHM. I don't
> > quite remember, but it's something like that.
> > Note that this might mean that the firmware watchdog in the driver will trigger,
> > as that's enabled by the open-source-firmware-flag. We might want to temporarly
> > disable the watchdog in the driver for the time being.
>
> I like the idea of encoding the capabilities in the firmware as it
> would be a self-documenting method as the firmware evolves.
>
> 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.
Already implemented here:
http://bu3sch.de/patches/wireless-testing/20081227-1821/patches/008-b43-probe-open-fw.patch
I just need to fix a leak in an error path before pushing that upstream.
--
Greetings, Michael.
next prev parent reply other threads:[~2009-01-15 16:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 15:30 [b43] opensource firmware Lorenzo Nava
2009-01-14 15:33 ` John W. Linville
2009-01-14 15:57 ` Buran Ayuthia
2009-01-14 16:06 ` Lorenzo Nava
2009-01-14 17:43 ` Larry Finger
2009-01-14 17:48 ` Michael Buesch
2009-01-15 9:10 ` Lorenzo Nava
2009-01-15 9:45 ` gavron
2009-01-15 10:20 ` Lorenzo Nava
2009-01-14 20:45 ` Johannes Berg
2009-01-14 21:09 ` John W. Linville
2009-01-14 21:20 ` Johannes Berg
2009-01-14 21:32 ` Kyle McMartin
2009-01-15 15:37 ` Michael Buesch
2009-01-15 15:44 ` Michael Buesch
2009-01-15 15:59 ` Larry Finger
2009-01-15 16:09 ` Michael Buesch [this message]
2009-01-15 23:17 ` Kyle McMartin
2009-01-16 15:15 ` Michael Buesch
2009-01-15 23:01 ` Francesco Gringoli
2009-01-16 15:12 ` Michael Buesch
2009-01-21 17:29 ` Francesco Gringoli
2009-01-21 17:36 ` Michael Buesch
2009-01-25 18:37 ` Rafał Miłecki
-- strict thread matches above, loose matches on Subject: below --
2009-01-09 10:29 Fwd: " Michael Buesch
2009-01-09 10:49 ` Michael Buesch
2009-01-09 10:58 ` Michael Buesch
2009-01-09 11:03 ` Francesco Gringoli
2009-01-09 11:00 ` Francesco Gringoli
2009-01-09 11:06 ` Michael Buesch
2009-01-09 11:11 ` Lorenzo Nava
2009-01-09 11:35 ` Lorenzo Nava
2009-01-10 17:37 ` Lorenzo Nava
2009-01-11 1:21 ` Buran Ayuthia
2009-01-12 15:39 ` John W. Linville
2009-01-12 15:48 ` Michael Buesch
2009-01-12 15:48 ` Francesco Gringoli
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=200901151709.49811.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=kyle@infradead.org \
--cc=linux-wireless@vger.kernel.org \
/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).