From: Larry Finger <Larry.Finger@lwfinger.net>
To: "P.G. Richardson" <p.g.richardson@phantomjinx.co.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtl8187 performance diagnostics
Date: Sun, 01 Mar 2009 13:29:46 -0600 [thread overview]
Message-ID: <49AAE22A.3080808@lwfinger.net> (raw)
In-Reply-To: <60836.82.152.175.172.1235929727.squirrel@www.phantomjinx.co.uk>
P.G. Richardson wrote:
> Is there anything I can do to help improve this situation? These results
> seems to rule out hardware in favour of being driver related. Are there
> other tests I could perform to determine where the fragility lies?
>
> Any thoughts, let me know.
OK, the Windows driver is better than the Linux one. Unfortunately, source is
not available.
You can check what we did when the RTL8187B was implemented. To do that, you
need to download the Realtek vendor-written Linux driver and check what they do
against what is in the current in-kernel driver. The critical areas will likely
be associated with power settings for the radio. Be aware that their code is
quite difficult to read as it has multiple conditional compilations that are
hard to keep straight.
I will be happy to test any improvements that you suggest.
Larry
next prev parent reply other threads:[~2009-03-01 19:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 21:00 rtl8187 cannot fix rate P.G. Richardson
2009-02-17 21:09 ` Larry Finger
2009-02-17 22:53 ` P.G. Richardson
2009-02-17 23:15 ` Larry Finger
2009-02-20 0:15 ` P.G. Richardson
2009-02-20 2:40 ` Larry Finger
2009-02-20 23:42 ` P.G. Richardson
2009-02-21 0:14 ` Larry Finger
2009-02-22 12:30 ` P.G. Richardson
2009-03-01 17:48 ` rtl8187 performance diagnostics (was: rtl8187 cannot fix rate) P.G. Richardson
2009-03-01 19:29 ` Larry Finger [this message]
2009-03-01 19:59 ` rtl8187 performance diagnostics P.G. Richardson
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=49AAE22A.3080808@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=p.g.richardson@phantomjinx.co.uk \
/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).