From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Joshua Smith <jesmith@kaon.com>
Cc: linux-wireless@vger.kernel.org,
rt2x00 Users List <users@rt2x00.serialmonkey.com>
Subject: Re: Question about starting up an AP
Date: Sat, 25 Sep 2010 10:34:24 +0200 [thread overview]
Message-ID: <201009251034.24993.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <DA0C92FD-F6BF-4746-9BE1-A643A0D70F7A@kaon.com>
Hi Joshua,
Am Freitag 24 September 2010 schrieb Joshua Smith:
> I'm building an AP using the latest CW code with a 2.6.27.8 kernel, and a
> Linsys/Cisco WMP660N PCI adapter. I'm having a problem with the boot-up
> sequence. Sometimes, when I start hostapd, I get this error in the system
> log:
>
> kernel: phy0 -> rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
>
> and hostapd craps out. If I try to run hostapd again, the kernel dies.
Hmm, the legacy driver waits much longer (100 * 1ms) for DMA being ready then
we do in rt2800 (5 * 1ms). Not sure if that will make a difference for you
but please try this patch:
>From d9792259cfc5253725f3855bb2cb9b4acadec103 Mon Sep 17 00:00:00 2001
From: Helmut Schaa <helmut.schaa@googlemail.com>
Date: Sat, 25 Sep 2010 10:32:21 +0200
Subject: [PATCH] rt2x00: increase wait time for WPDMA being ready
Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
---
drivers/net/wireless/rt2x00/rt2800lib.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/rt2x00/rt2800lib.c b/drivers/net/wireless/rt2x00/rt2800lib.c
index c7076de..058de10 100644
--- a/drivers/net/wireless/rt2x00/rt2800lib.c
+++ b/drivers/net/wireless/rt2x00/rt2800lib.c
@@ -277,7 +277,7 @@ int rt2800_wait_wpdma_ready(struct rt2x00_dev *rt2x00dev)
unsigned int i;
u32 reg;
- for (i = 0; i < REGISTER_BUSY_COUNT; i++) {
+ for (i = 0; i < 100; i++) {
rt2800_register_read(rt2x00dev, WPDMA_GLO_CFG, ®);
if (!rt2x00_get_field32(reg, WPDMA_GLO_CFG_TX_DMA_BUSY) &&
!rt2x00_get_field32(reg, WPDMA_GLO_CFG_RX_DMA_BUSY))
--
1.7.1
next prev parent reply other threads:[~2010-09-25 8:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 19:25 Question about starting up an AP Joshua Smith
2010-09-25 8:18 ` Helmut Schaa
2010-09-25 8:34 ` Helmut Schaa [this message]
[not found] ` <B17955D1-62BE-4A7E-8ECD-05FA62BD80B9@kaon.com>
2010-09-27 17:56 ` Helmut Schaa
2010-09-27 19:21 ` Joshua Smith
2010-09-27 19:43 ` Helmut Schaa
2010-09-27 20:26 ` Joshua Smith
2010-09-27 20:35 ` Helmut Schaa
2010-09-29 18:21 ` Joshua Smith
2010-09-30 15:52 ` Joshua Smith
2010-09-30 16:14 ` Helmut Schaa
2010-10-01 5:42 ` Helmut Schaa
2010-10-14 17:16 ` Joshua Smith
2010-10-15 9:46 ` Helmut Schaa
2010-10-15 13:36 ` Joshua Smith
2010-10-26 9:35 ` Helmut Schaa
2010-10-26 9:41 ` Johannes Berg
2010-10-26 10:04 ` Helmut Schaa
2010-10-26 11:34 ` Ivo Van Doorn
2010-09-27 19:46 ` Helmut Schaa
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=201009251034.24993.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=jesmith@kaon.com \
--cc=linux-wireless@vger.kernel.org \
--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).