From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John Linville <linville@tuxdriver.com>,
Michael Buesch <mb@bu3sch.de>, Mark Huijgen <mark@huijgen.tk>,
Broadcom Wireless <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] b43: Add LP-PHY firmware loading support
Date: Fri, 14 Aug 2009 17:26:48 +0200 [thread overview]
Message-ID: <69e28c910908140826v6725a109u1d6e827869c4ffff@mail.gmail.com> (raw)
In-Reply-To: <4A85678E.6080205@lwfinger.net>
(Restored CCs.)
2009/8/14 Larry Finger <Larry.Finger@lwfinger.net>:
> Gábor Stefanik wrote:
>>
>> On http://bu3sch.de/gitweb?p=b43-tools.git;a=blob;f=fwcutter/fwcutter_list.h;hb=HEAD,
>> it doesn't look like v4.150.10.5 contains rev16 - there is one version
>> that does have it, but the link to that file is dead.
>
> The rev 16 firmware definitely is in driver 4.174.64.19, but not in
> 4.150.10.5. I'll have to figure out where I got it, and what
> modifications are needed in fwcutter to make it available.
>
> I suggest that you do the mods to the firmware loading. If Broadcom
> has it in their driver, there must be hardware that needs it.
>
> Larry
I would say that's a goal for later - the FIFO sizes are different, so
it would clearly need more work than just loading the firmware to
support rev16 devices.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
next prev parent reply other threads:[~2009-08-14 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 11:51 [PATCH] b43: Add LP-PHY firmware loading support Gábor Stefanik
2009-08-14 12:11 ` Mark Huijgen
2009-08-14 13:00 ` Larry Finger
2009-08-14 13:02 ` Gábor Stefanik
2009-08-14 13:10 ` Larry Finger
[not found] ` <69e28c910908140623r6f158a89pcf145bad7b244af8@mail.gmail.com>
[not found] ` <4A85678E.6080205@lwfinger.net>
2009-08-14 15:26 ` Gábor Stefanik [this message]
2009-08-14 20:17 ` Michael Buesch
2009-08-14 20:20 ` Gábor Stefanik
2009-08-14 20:41 ` Michael Buesch
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=69e28c910908140826v6725a109u1d6e827869c4ffff@mail.gmail.com \
--to=netrolller.3d@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mark@huijgen.tk \
--cc=mb@bu3sch.de \
/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).