From: Dan Williams <dcbw@redhat.com>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: dsd@laptop.org, libertas-dev@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: poor performance with W2CBW003 (Marvell 8686)
Date: Tue, 12 Jun 2012 14:18:54 -0500 [thread overview]
Message-ID: <1339528734.14638.14.camel@dcbw.foobar.com> (raw)
In-Reply-To: <1339247007.5895.373.camel@localhost>
On Sat, 2012-06-09 at 15:03 +0200, Andreas Kemnade wrote:
> Hi,
>
> on the GTA04 (www.gta04.org)
> which has a W2CBW003 chip for wifi connected to a DM3730CBP CPU. data
> rates are quite low using the libertas driver from kernel 3.2-3.4
> (https://github.com/neilbrown/gta04/branches)
> even near an accesspoint. That seems not depend on the encryption
> settings. Rates are around 100KByte/s. iwconfig shows 5.5Mb/s if it is
> not connected to an accesspoint with specially configured rates (but
> still the throughput is low).
>
> In contrary data rates are high (>1MByte/s) with a kernel based on
> the 2.6.32 BeagleBoard XM hw-validation kernel
> https://github.com/goldelico/gta04-kernel
> That behaviour was reported by several people.
>
> I tried also the libertas-tf driver with kernel 3.2 using the
> instructions here:
> http://corysohrakoff.wordpress.com/2011/09/13/enabling-wifi-ap-mode-on-a-gumstix-overo/
> That was also slow.
>
> Any hints?
GSPI or SDIO? What SD host controller? Does the controller support
4-bit mode correctly? What block sizes does it support? Most often the
issue is with crappy host controllers that need workarounds or quirks
to correctly support the higher speeds that the driver can do. The
benchmark I always used was that on a laptop with a Ricoh SD controller,
I could easily pull megabits per second even 15 feet away.
(that's not to say there aren't inefficiencies in the driver, just that
we know that given a good SDHC and a good SDHC driver, that the libertas
driver itself is not the bottleneck).
Dan
next prev parent reply other threads:[~2012-06-12 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 13:03 poor performance with W2CBW003 (Marvell 8686) Andreas Kemnade
2012-06-12 19:18 ` Dan Williams [this message]
2012-06-12 22:16 ` Andreas Kemnade
2012-06-13 17:06 ` hong zhang
2012-06-13 17:42 ` Andreas Kemnade
2012-06-13 18:39 ` hong zhang
2012-06-14 5:45 ` Andreas Kemnade
2012-06-14 16:11 ` hong zhang
2012-06-14 16:30 ` hong zhang
2012-06-15 6:18 ` Andreas Kemnade
2012-06-15 14:56 ` hong zhang
2012-06-15 16:48 ` Dan Williams
2012-10-29 17:10 ` Martin Chaplet
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=1339528734.14638.14.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=andreas@kemnade.info \
--cc=dsd@laptop.org \
--cc=libertas-dev@lists.infradead.org \
--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).