All of lore.kernel.org
 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: Mon, 01 Jun 2009 17:17:05 -0500	[thread overview]
Message-ID: <4A245361.9060807@lwfinger.net> (raw)
In-Reply-To: <4A244C5A.50307@free.fr>

matthieu castet wrote:
> Larry Finger wrote:
>> 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.
> Ok but what prevent b43 to support core 4 chip with v4 firmware like the
> broadcom driver does ?
> I am aware that the current driver doesn't support it, but what are the
> missing part to support it ?

The firmware loader code is the first step. Beyond that, I have no idea.

> If it is the difference from core4 from newer chip, why b43legacy
> contains only few special case for core4 chip.

I do not know other than that is what the specs called for.

> PS : I don't have core 4 chip nor plan to get some, I ask this out of
> curiosity.

I do have such a chip, but I use it to verify b43legacy code.

Larry


  reply	other threads:[~2009-06-01 22:17 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
2009-06-01 21:47   ` matthieu castet
2009-06-01 22:17     ` Larry Finger [this message]
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=4A245361.9060807@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.