linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Denis 'GNUtoo' Carikli" <GNUtoo@no-log.org>,
	"Larry Finger" <Larry.Finger@lwfinger.net>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	"Kan Yan" <kanyan@broadcom.com>,
	wireless <linux-wireless@vger.kernel.org>,
	brcm80211-dev-list@broadcom.com
Subject: Re: Question about BCM43228 and outdated description in MAINTAINERS
Date: Wed, 27 Jun 2012 09:49:47 +0200	[thread overview]
Message-ID: <4FEABB1B.90005@broadcom.com> (raw)
In-Reply-To: <4FE8D9F7.7070707@hauke-m.de>

On 06/25/2012 11:36 PM, Hauke Mehrtens wrote:
>> I suspect 0846:9020 can be *not* a BCM43231. I discovered some other
>> > chipset on this USB dongle when hacking it with brcmfmac. If I
>> > remember correctly it was 4322. Sounds a little weird, as we already
>> > know softmac BCM4322 with N-PHY, I don't know if there is any relation
>> > between softmac 4322 and fullmac 4322.

The BCM43231 dongle is indeed bcm4322. Not sure whether the chip
revisions are different.

> I have two BCM4322 soldered on a board of a router (Linksys WRT610N V1)
> and connected via PCI to the main Chip (BCM4705/BCM4785). My BCM4322 has
> a ARM Cortex M3 core, a USB host core, a PCI and a PCIe core in addition
> to the "normal cores". My BCM4322 is running as a softmac device and is
> supported by b43 and ssb, 2.4 Ghz wifi is working.
> 
> This chip is probably capable of running in softmac mode on a PCI or
> PCIe card or in fullmac mode in a USB dongle, at least that's my
> explanation for the ARM core on this device.

The chip has some redundant cores. Which these are indeed depends on the
type of host interface used. It is a trade-off between this and spin a
separate chip.

However, in case of USB it is not a fullmac driver model and not in
softmac driver model either. It has a different functional split of mac
functionality between host and firmware. This is also true for the
bcm43236 v2. Also this model has been abandoned for new devices.

This would need a cfg80211 driver duplicating mac80211 functionality or
wish the mac80211 offload features match the functional split nicely.
Internally we have looked at the mac80211 offloads and concluded it was
not. Hence we decided to only support softmac and fullmac driver models.

Gr. AvS



  reply	other threads:[~2012-06-27  7:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 15:41 Question about BCM43228 and outdated description in MAINTAINERS Larry Finger
2012-06-25 16:13 ` Hauke Mehrtens
2012-06-25 20:03   ` Denis 'GNUtoo' Carikli
2012-06-25 20:22     ` Hauke Mehrtens
2012-06-25 21:25       ` Rafał Miłecki
2012-06-25 21:36         ` Hauke Mehrtens
2012-06-27  7:49           ` Arend van Spriel [this message]
2012-06-27  8:37 ` Arend van Spriel
2012-06-27 12:18   ` Rafał Miłecki
2012-06-27 15:07   ` Larry Finger

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=4FEABB1B.90005@broadcom.com \
    --to=arend@broadcom.com \
    --cc=GNUtoo@no-log.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=kanyan@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@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).