From: "Arend van Spriel" <arend@broadcom.com>
To: "Larry Finger" <Larry.Finger@lwfinger.net>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Francesco Gringoli" <francesco.gringoli@ing.unibs.it>,
b43-dev <b43-dev@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Performance of BCM43224 (14e4:4353)
Date: Fri, 9 Dec 2011 18:32:05 +0100 [thread overview]
Message-ID: <4EE24615.9020003@broadcom.com> (raw)
In-Reply-To: <4EE23AF5.8000400@lwfinger.net>
On 12/09/2011 05:44 PM, Larry Finger wrote:
> On 12/09/2011 04:27 AM, Arend van Spriel wrote:
>>
>> Hi Larry
>>
>> Could you perform your benchmark test on brcmsmac without the bcma
>> patches. It kind of surprises me that we are that far off compared to
>> the wl driver.
>
> I wondered about that myself. Upon investigation, my test with bcma/brcmsmac
> never worked. Without the patches, my netperf numbers for brcmsmac are RX 40.0
> and TX 59.7 Mbps.In all cases, the reported number is the maximum of 10 tries of
> 3 sec each.
Hi, Larry
That numbers do make more sense. Thanks for testing.
> With the patches, my dmesg contains the following:
>
> [ 908.282281] bcma: Bus registered
> [ 908.353242] brcmsmac bcma0:0: mfg 4bf core 812 rev 23 class 0 irq 22
> [ 908.380164] ieee80211 phy0: wl0: brcms_b_attach: si_attach failed
> [ 908.380184] ieee80211 phy0: wl0: brcms_b_attach: failed with err 11
> [ 908.380192] ieee80211 phy0: wl0: brcms_c_attach: failed with err 11
> [ 908.380316] ieee80211 phy0: brcmsmac: attach() failed with code 11
> [ 908.380379] brcmsmac: brcms_bcma_probe: brcms_attach failed!
> [ 908.381715] brcms_module_init: register returned 0
That is too bad. I thought all individual commits were ok, but I
reordered some. It could be the srom code failing, which will likely
become redundant as bcma can provide the info.
> As b43 is also loaded, which may be a second problem, it is run instead of brcmsmac.
With the submitted patches brcmsmac claims any revision of 802.11 cores.
Not sure what b43 claims. I have a patch internally to claim only
revisions 23 and 24, which are used in bcm43224, bcm43225, and bcm4313.
Gr. AvS
next prev parent reply other threads:[~2011-12-09 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 0:46 Performance of BCM43224 (14e4:4353) Larry Finger
2011-12-09 9:16 ` Arend van Spriel
2011-12-09 10:27 ` Arend van Spriel
2011-12-09 16:44 ` Larry Finger
2011-12-09 17:32 ` Arend van Spriel [this message]
2011-12-09 17:57 ` Larry Finger
2011-12-09 19:31 ` Arend van Spriel
2011-12-09 20:06 ` Larry Finger
2011-12-09 18:17 ` Larry Finger
2011-12-09 20:04 ` Arend van Spriel
2011-12-09 22:53 ` Larry Finger
2011-12-10 9:18 ` Rafał Miłecki
2011-12-10 11:04 ` Arend van Spriel
2011-12-10 19:49 ` Larry Finger
2011-12-10 20:28 ` Arend van Spriel
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=4EE24615.9020003@broadcom.com \
--to=arend@broadcom.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=francesco.gringoli@ing.unibs.it \
--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).