From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: brcm80211-dev-list <brcm80211-dev-list@broadcom.com>,
Brett Rudley <brudley@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>,
linux-wireless@vger.kernel.org, Franky Lin <frankyl@broadcom.com>,
Arend van Spriel <arend@broadcom.com>
Subject: Re: TCP data throughput for BCM43362
Date: Wed, 12 Oct 2016 22:48:13 +0200 [thread overview]
Message-ID: <1476305293.2065.1.camel@embedded.rocks> (raw)
In-Reply-To: <c571ac91-ccd1-5e98-317f-eb3e56ad6b58@broadcom.com>
On Wed, 2016-10-12 at 21:08 +0200, Arend van Spriel wrote:
[snip]
>
> You referred to 20 Mbps claim on wiced dev kit page at mouser so I
> assumed you were using that and it includes firmware. As you
> confirmed
> using firmware from linux-firmware repo this question does not
> matter.
Note, that a user reported "low" throughput on i.MX28 (same processor I
use with BCM43362) using Qualcom/Atheros QCA 6124 only seeing 20MB
using iperf [1].
[1] https://community.nxp.com/thread/353921
Best regards
Jörg Krause
prev parent reply other threads:[~2016-10-12 20:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 20:46 TCP data throughput for BCM43362 Jörg Krause
[not found] ` <CAF7Mx6o+WuQqtzuApMWQ8YAkLSX7xQ_H06xmO--RxFdwHwzLdQ@mail.gmail.com>
2016-08-05 21:29 ` Jörg Krause
[not found] ` <CA+8PC_f7VQMwBfQmZZ_vUtYtNJKVYzmFmxziAwoG8-iRUeW9Jw@mail.gmail.com>
2016-08-06 8:07 ` Jörg Krause
2016-08-06 14:12 ` Jörg Krause
2016-08-07 11:41 ` Arend van Spriel
2016-08-12 9:25 ` Jörg Krause
2016-08-22 13:37 ` Jörg Krause
2016-08-24 18:35 ` Arend Van Spriel
2016-08-29 21:15 ` Jörg Krause
2016-09-14 13:41 ` Jörg Krause
2016-09-14 18:13 ` Arend Van Spriel
2016-09-19 6:36 ` Jörg Krause
2016-09-21 14:15 ` Arend van Spriel
2016-09-22 8:09 ` Arend Van Spriel
2016-09-22 12:52 ` Jörg Krause
[not found] ` <CAF7Mx6q+B4RoURNF5XxewjF9aVGCXg==XU0aDD6w+354yXZ70Q@mail.gmail.com>
2016-10-11 6:14 ` Jörg Krause
2016-10-12 8:11 ` Arend Van Spriel
2016-10-12 14:27 ` Jörg Krause
2016-10-12 19:08 ` Arend van Spriel
2016-10-12 19:30 ` Jörg Krause
[not found] ` <CAF7Mx6rqfbhDL-MRZ93vzCdSskgqi_bVNn=1SGb_WKV=DZZ+YQ@mail.gmail.com>
2016-10-12 21:19 ` Jörg Krause
[not found] ` <CAF7Mx6pD5VZ57PHy5DSj8yLOLY4vir2JhEdEL8SB3kr91OqFsQ@mail.gmail.com>
2016-10-12 22:50 ` Jörg Krause
2016-10-12 20:48 ` Jörg Krause [this message]
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=1476305293.2065.1.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=arend.vanspriel@broadcom.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.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 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.