From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Kevin Lo <kevlo@kevlo.org>, John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] [PATCH] rt2x00: rt2800lib: update RF registers for RT5390
Date: Thu, 24 Oct 2013 18:40:43 +0200 [thread overview]
Message-ID: <52694D8B.1030308@01019freenet.de> (raw)
In-Reply-To: <20131024052408.GA7828@ns.kevlo.org>
Hi Kevin,
Kevin Lo wrote:
> Mirror the latest MediaTek/Ralink driver with respect to RT5390 RF register
> programming. The PCI and USB devices use different init values.
If you (and others here) really want to improve anything for rt2800usb,
change your development system and use a raspberry pi (PI).
Why PI? Because the PI doesn't cover any broken code / concept / driver
architecture with hardware resources.
You want to have an example?
This device[1] achieves 140 MBit/s (data receiving) on the PI, measured
with netperf and rt5572sta compared to rt2800usb, which achieves very
very very poor 30 MBit/s(! - even w/ best radio conditions can't be
achieved any more) but an extremely high CPU load at the same time!
If you compare the basic behaviour of rt5572sta and rt2800usb, you will
see, that rt5572sta uses a completely different usb handling, which
doesn't need that much CPU resources as the one used by rt2800usb.
Therefore: If you really want to improve rt2800usb, at first take a
serious look at how usb is handled by rt5572sta and how to save CPU
resources.
In a nutshell: Use a few, but big USB packets instead of a lot of small
ones, which needs a lot of interrupts / s and therefore needs a lot of
CPU resources - which aren't available on the PI at all.
Kind regards,
Andreas
[1] http://wikidevi.com/wiki/Linksys_AE3000
next prev parent reply other threads:[~2013-10-24 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 5:24 [PATCH] rt2x00: rt2800lib: update RF registers for RT5390 Kevin Lo
2013-10-24 16:40 ` Andreas Hartmann [this message]
2013-10-25 2:03 ` [rt2x00-users] " Kevin Lo
2013-10-27 16:29 ` Andreas Hartmann
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=52694D8B.1030308@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=kevlo@kevlo.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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).