From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Lorenzo Nava <navalorenx@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [b43] opensource firmware
Date: Wed, 14 Jan 2009 18:48:21 +0100 [thread overview]
Message-ID: <200901141848.21574.mb@bu3sch.de> (raw)
In-Reply-To: <496E243F.1080500@lwfinger.net>
On Wednesday 14 January 2009 18:43:27 Larry Finger wrote:
> Lorenzo Nava wrote:
>
> > 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!
>
> On my BCM4318 (Linksys WPC54G, Ver 3) in a Cardbus format in a
> WPA2-personal encrypted network with AES algorithm, it nearly worked.
> With your firmware, it can scan and authenticate. It even gets an
> DHCP-supplied IP address; however, I get no data through the link. In
> addition, I see lots of PHY TRANSMISSION ERRORS. When I disable
> hardware encryption (nohwcrypt=1), then it works.
Support for hardware crypto would require to reverse engineer the PCM firmware, first.
So we can't support hw-crypto, except on new devices that don't have a PCM anymore.
But these are not rev5 cores :)
--
Greetings, Michael.
next prev parent reply other threads:[~2009-01-14 17:48 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 [this message]
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=200901141848.21574.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=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).