linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Lorenzo Nava <navalorenx@gmail.com>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [b43] opensource firmware
Date: Wed, 14 Jan 2009 10:33:56 -0500	[thread overview]
Message-ID: <20090114153355.GB3854@tuxdriver.com> (raw)
In-Reply-To: <9FB118DA-845D-4708-84F3-4D51837D8C68@gmail.com>

On Wed, Jan 14, 2009 at 04:30:47PM +0100, Lorenzo Nava wrote:
> Hello everybody,
> 
> we completed the 1st version of initvals. They are available at http://www.ing.unibs.it/openfwwf 
> . Currently only binary version is available: don't worry, we will  
> publish source code as soon as possible!! This first version is a  
> "test version": please try it and let us know if everythink is ok...
> 
> Today we have also tested a new firmware version that works with WPA2- 
> personal (both TKIP and CCMP) and WPA2-enterprise (EAP-TTLS) (tested  
> on 4306 and 4318 PCI device). If anybody was interested please try new  
> firmware with encryption and let us know if it works correctly, thanks!
> 
> Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf

Awesome...awesome...awesome!!!

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-01-14 15:45 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 [this message]
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
  -- 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=20090114153355.GB3854@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --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).