From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: bruno randolf <bruno@thinktube.com>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, jirislaby@gmail.com, mcgrof@gmail.com
Subject: Re: [ath5k-devel] [PATCH 6/8] ath5k: Fixes for PCI-E cards
Date: Mon, 25 Feb 2008 23:39:02 -0500 [thread overview]
Message-ID: <20080226043902.GA11185@hash.localnet> (raw)
In-Reply-To: <40f31dec0802251957o3b5b542vb5bf591fa2e73599@mail.gmail.com>
On Tue, Feb 26, 2008 at 05:57:22AM +0200, Nick Kossifidis wrote:
> Bob try removing this and see what happens (in terms of
> performance/stability)...
>
> if (ath5k_hw_register_timeout(ah, AR5K_PHY_AGCCTL,
> AR5K_PHY_AGCCTL_CAL, 0, false)) {
> ATH5K_ERR(ah->ah_sc, "calibration timeout (%uMHz)\n",
> channel->center_freq);
> return -EAGAIN;
> }
It doesn't really have an effect, because even without this, the noise
floor calibration fails anyway. I suspect by the time it gets in this
state the device is just hung generally.
So, I can't sustain a connection long enough to do iperf. I got numbers
from madwifi though :)
Seems when it gets a big hunk of data the device barfs. When I'm doing
something like ssh or just browsing a little, it's annoying but still
useable because most of the time it'll disassociate with the AP for a
few seconds, reassociate, and it's working again.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-02-26 4:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 15:43 [ath5k-devel] [PATCH 6/8] ath5k: Fixes for PCI-E cards Bob Copeland
2008-02-26 2:13 ` bruno randolf
2008-02-26 3:51 ` Bob Copeland
2008-02-26 3:57 ` Nick Kossifidis
2008-02-26 4:39 ` Bob Copeland [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-24 4:28 Nick Kossifidis
2008-02-24 4:45 ` [ath5k-devel] " Nick Kossifidis
2008-02-24 4:47 ` Nick Kossifidis
2008-02-24 16:09 ` Bob Copeland
2008-02-24 17:59 ` Bob Copeland
2008-02-24 18:58 ` Nick Kossifidis
2008-02-24 20:21 ` Bob Copeland
2008-02-24 23:23 ` Nick Kossifidis
2008-02-27 3:23 ` Luis R. Rodriguez
2008-02-27 5:54 ` Nick Kossifidis
2008-02-27 13:30 ` Luis R. Rodriguez
2008-02-27 15:52 ` John W. Linville
2008-02-27 18:44 ` Nick Kossifidis
2008-02-28 22:20 ` Luis R. Rodriguez
2008-02-24 23:48 ` Nick Kossifidis
2008-02-25 2:23 ` Bob Copeland
2008-02-25 14:20 ` Nick Kossifidis
2008-02-24 20:17 ` Christoph Hellwig
2008-02-24 23:27 ` Nick Kossifidis
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=20080226043902.GA11185@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=bruno@thinktube.com \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@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 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.