linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Matthieu CASTET <castet.matthieu@free.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: b43 vs b43legacy
Date: Fri, 29 May 2009 16:15:09 -0500	[thread overview]
Message-ID: <4A20505D.40908@lwfinger.net> (raw)
In-Reply-To: <loom.20090529T190620-42@post.gmane.org>

Matthieu CASTET wrote:
>
> what's the difference between b43 and b43legacy ?
> 
>>From a first point a view, it seems b43 is for core >= 5 and b43legacy for the
> other.
> There is also firmware difference : b43 need v4 and b43legacy need v3.

The firmware difference is the primary one.

> But v4 firmware seems to support core 4 (pcm4 & ucode4) and b43 code got some
> support for old chips (<5).

The Broadcom V4 drivers do have core 4 firmware embedded in them and it is
extracted by b43-fwcutter; however, b43 will _NOT_ work with core 4 chips. The
firmware loader will only find firmware for core 5 and later. On the other hand,
core 5 devices have been tested with b43legacy. I have a local patch that I use
to switch my 14e4:4312 device so that it uses b43legacy. This allows me to test
any changes.

> Is the split was made because nobody know how to use firmware v4 with core 4 or
> because core 4 it so different from newer core.
> In the latter case why code for older chip (<5) is not removed from the driver ?

>From what I have heard, the older chips do not have the on-board memory to run
V4 firmware. Certainly, any chips that have core 2 cannot handle V4 firmware.

I suspect that any residual code for older chips left in b43 was missed. If you
want to prepare patches to remove such code, please do.

Larry

  parent reply	other threads:[~2009-05-29 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 19:19 b43 vs b43legacy Matthieu CASTET
2009-05-29 20:42 ` Luis R. Rodriguez
2009-05-29 21:15 ` Larry Finger [this message]
2009-06-01 21:47   ` matthieu castet
2009-06-01 22:17     ` Larry Finger
2009-06-02 15:17     ` Michael Buesch
2009-06-08 19:43       ` matthieu castet
2009-05-30  8:58 ` 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=4A20505D.40908@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=castet.matthieu@free.fr \
    --cc=linux-wireless@vger.kernel.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).