From: Paul Hampson <Paul.Hampson@Pobox.com>
To: netdev@vger.kernel.org
Cc: public-linville-2XuSBdqkA4R54TAoqtyWWQ@ciao.gmane.org,
Michael Buesch <public-mb-fseUSCV1ubazQB+pC5nmwQ@ciao.gmane.org>
Subject: Re: [PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast)
Date: Fri, 17 Nov 2006 19:49:47 +1100 [thread overview]
Message-ID: <455D77AB.907@Pobox.com> (raw)
In-Reply-To: <1163750573.5826.7.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> On Fri, 2006-11-17 at 08:53 +0100, Johannes Berg wrote:
>> On Fri, 2006-11-17 at 18:46 +1100, Benjamin Herrenschmidt wrote:
>>> So what is the solution for Apple machines owner who only get a v3
>>> firmware from Apple ? I remember you telling me the answer on irc but I
>>> wanted to make it public :-) Some web site we can d/l the windows
>>> updates and extract the FW ?
>> Yes, fwcutter comes with a huge list of URLs for both firmware versions
>> (I suppose they'll remove the v3 ones now...)
v3 ones are still needed for the softmac version, unless I'm badly drunk...
> Well, the latest "released" version (fwcutter-005) contains a huge list
> of ... v3 URLs :-) Only 2 v4 in there. I'll check SVN.
There's actually a v4 big-endian firmware in the fwcutter list in SVN, but
no URL to fetch it from...
It comes from the AppleAirPortBrcm4311 driver. I've no idea where that update
comes from, I found a copy on the Internet somewhere. (I think someone posted
the file to a message board looking for help with it...)
I'm not sure, would it be be bad for me to just stick a copy of it up on a
website? If so, I can prolly dig up the place I got it from (I'm sure I
bookmarked it at the time) and people can choose their own level of comfort.
I have to say it's not clear from the documentation that BE machines like
PPC need to use a BE firmware... (If that's not the case, it's not clear
that it's not the case either, it just doesn't say either way. ^_^)
In fact, given that it's a BE firmware update for Intel-based Macs' bcm
cards, I presume the endianess of the firmware doesn't matter?
--
Paul Hampson
Paul.Hampson@Pobox.com
next prev parent reply other threads:[~2006-11-17 8:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 22:23 bcm43xx-d80211 broadcast reception with WPA Paul Hampson
2006-11-10 8:27 ` Ivo Van Doorn
2006-11-10 9:24 ` Paul Hampson
2006-11-10 20:12 ` Michael Buesch
2006-11-11 6:32 ` Paul Hampson
2006-11-11 15:07 ` Michael Buesch
2006-11-12 1:24 ` Paul TBBle Hampson
2006-11-12 8:34 ` Michael Buesch
2006-11-12 20:43 ` Ismail Donmez
2006-11-12 21:47 ` Michael Buesch
2006-11-12 22:40 ` Ismail Donmez
2006-11-12 22:41 ` Ismail Donmez
2006-11-12 22:54 ` Johannes Berg
2006-11-13 8:10 ` Ismail Donmez
2006-11-13 10:43 ` Jiri Benc
2006-11-14 14:29 ` Paul TBBle Hampson
2006-11-14 14:40 ` Johannes Berg
2006-11-14 15:53 ` Michael Buesch
2006-11-14 14:40 ` Paul TBBle Hampson
2006-11-14 14:41 ` Johannes Berg
2006-11-15 18:48 ` [PATCH, RFT]: Fix bcm43xx-d80211 hwcrypto (was Re: bcm43xx-d80211 broadcast reception with WPA) Michael Buesch
2006-11-16 12:34 ` [PATCH, RFT]: Fix bcm43xx-d80211 hwcrypto Paul TBBle Hampson
2006-11-16 14:07 ` [PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast) Michael Buesch
[not found] ` <200611161507.33971.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-11-17 7:46 ` Benjamin Herrenschmidt
2006-11-17 7:53 ` Johannes Berg
2006-11-17 8:02 ` Benjamin Herrenschmidt
2006-11-17 8:49 ` Paul Hampson [this message]
2006-11-17 10:35 ` Andreas Schwab
[not found] ` <jeveles6lx.fsf-+JVCjXrnBTholqkO4TVVkw@public.gmane.org>
2006-11-17 11:04 ` Johannes Berg
2006-11-17 11:30 ` Andreas Schwab
2006-11-17 22:59 ` Martin Langer
2006-11-17 13:20 ` Paul TBBle Hampson
2006-11-18 1:15 ` Paul TBBle Hampson
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=455D77AB.907@Pobox.com \
--to=paul.hampson@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=public-linville-2XuSBdqkA4R54TAoqtyWWQ@ciao.gmane.org \
--cc=public-mb-fseUSCV1ubazQB+pC5nmwQ@ciao.gmane.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).