From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Lorenzo Nava <navalorenx@gmail.com>,
linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de,
Gringoli PhD Gringoli <francesco.gringoli@ing.unibs.it>
Subject: Re: [b43] opensource firmware
Date: Mon, 12 Jan 2009 16:48:04 +0100 [thread overview]
Message-ID: <200901121648.05069.mb@bu3sch.de> (raw)
In-Reply-To: <20090112153949.GC31525@tuxdriver.com>
On Monday 12 January 2009 16:39:49 John W. Linville wrote:
> On Sat, Jan 10, 2009 at 06:37:43PM +0100, Lorenzo Nava wrote:
> > Hello everybody,
> >
> > today I tried OpenFWWF with kernel 2.6.28 on a Siemens wifi device with
> > Broadcom 4306 chipset:
> >
> > BCM94306 802.11g (rev 03)
> > PHY: Analog 2, Type 2, Revision 2
> > Radio: Manuf 0x17F, Version 0x2050, Revision 2
> >
> > I did some tests and everything seems to work fine.
> >
> > I remember, once again, that OpenFWWF needs v480 initvals to work
> > properly, and was tested on 2.6.27-rc5 kernel.
>
> Any chance on getting a set of initvals packaged with the open source
> firmware? That would allow distros like Fedora to package this...
Did anybody try with the set of initvals from my git repository?
It includes the major parts. It just misses parts like the default-beacon-template
and stuff. But that's not really needed for now.
--
Greetings, Michael.
next prev parent reply other threads:[~2009-01-12 15:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 10:29 Fwd: [b43] opensource firmware 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 [this message]
2009-01-12 15:48 ` Francesco Gringoli
2009-01-09 11:12 ` Fwd: " David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2009-01-14 15:30 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
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
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=200901121648.05069.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=francesco.gringoli@ing.unibs.it \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=navalorenx@gmail.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).