From: Brent Taylor <btaylor1@motorolasolutions.com>
To: linux-wireless@vger.kernel.org
Subject: ATH6KL lockup during init
Date: Tue, 26 Jul 2011 15:43:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20110726T174149-11@post.gmane.org> (raw)
I’m a developer working with the Atheros AR6003 Wireless LAN chip. I recently
updated the Linux kernel on my custom board to 3.0.0 and pulled the latest
snapshot of the ath6kl driver from
http://git.kernel.org/?p=linux/kernel/git/kvalo/ath6kl-cleanup.git;a=summary (as
of 2011-07-25). I’m also using the latest firmware images from
http://www.kernel.org/pub/linux/kernel/people/mcgrof/firmware/ath6k.tar.gz as
recommended by
http://wireless.kernel.org/en/users/Drivers/ath6kl?highlight=%28ar6003%29.
After running 'insmod ath6kl.ko', the command line hangs. I’ve narrowed down
the execution path to the function ath6kl_bmi_get_rx_lkahd (called from
ath6kl_bmi_exeute after loading the OPT firmware). The parameter value of
"need_timeout" is set to false. Without this timeout the function never
returns. The call to ath6kl_hif_read_write_sync always returns 0, and the value
of rx_word is always 0.
My question is: What would cause the read from address
RX_LOOKAHEAD_VALID_ADDRESS to always return a value of 0?
My custom board is using an atmel at91sam9g45 microprocessor using the SDIO bus
on mci1. Any information would be greatly appreciated.
Thanks,
Brent Taylor
Senior Software Developer
Applied Technology Department of Motorola Solutions
btaylor1@motorolasolutions.com
next reply other threads:[~2011-07-26 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 15:43 Brent Taylor [this message]
2011-07-27 5:19 ` ATH6KL lockup during init Vasanthakumar Thiagarajan
2011-07-27 12:51 ` Brent Taylor
2011-08-02 5:59 ` Kalle Valo
2011-08-04 12:55 ` Brent Taylor
2011-09-13 6:29 ` Kalle Valo
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=loom.20110726T174149-11@post.gmane.org \
--to=btaylor1@motorolasolutions.com \
--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 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.