From: "Bob Copeland" <me@bobcopeland.com>
To: "Zack Weinberg" <zackw@panix.com>,
"Nick Kossifidis" <mickflemm@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: Getting ath5k driver working with Thinkpad T61 [168c:1014]
Date: Mon, 16 Jun 2008 11:24:42 -0400 [thread overview]
Message-ID: <E1K8GZW-0007vs-I1@hash.localnet> (raw)
> Attached. This has two attempts at 'iwlist wlan0 scan' in there
> before I shut it back down again. I see an awful lot of repetitive
> writes of the same value at the same address, but I don't know what
> this stuff means...
Thanks for the update. I haven't had a chance to look at this until
now, as I've been traveling the last couple of weeks. I'll go through
it this evening to see if anything jumps out.
FWIW, here's how to read the dump. Given a line like:
R 4 48.700287 1 0xdf3f9860 0x9d1a 0x0 0
>From left to right that would be:
Read 4 bytes at time 48.700287 (map id=1) the address 0xdf3f9860, and
receive the value 0x9d1a (the other two 0s are meaningless for now).
Writes look the same except start with W.
>From the address, you can figure out the register: in this case it is
0x9860 since the MMIO base address is 0xdf3f0000. Now you can look in
reg.h to find the name of that register if we know it (here it is
AR5K_PHY_AGCCTL).
Then you can look at the source for where that register is being used to
get an idea of what is going on. In the above case, we're reading the
register until the hardware completes AGC calibration and sets
AR5K_PHY_AGCCTL_CAL (bit 0) low - that eventually happens .02 seconds
later when the value 0x9d18 is read.
--
Bob Copeland %% www.bobcopeland.com
next reply other threads:[~2008-06-16 15:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 15:24 Bob Copeland [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-14 17:24 Getting ath5k driver working with Thinkpad T61 [168c:1014] Zack Weinberg
2008-05-14 18:38 ` Bob Copeland
2008-05-14 18:45 ` Zack Weinberg
2008-05-14 19:09 ` Bob Copeland
2008-05-15 14:41 ` Zack Weinberg
2008-05-15 16:45 ` Bob Copeland
2008-05-15 16:53 ` Zack Weinberg
2008-05-15 20:44 ` Bob Copeland
2008-05-15 19:44 ` Nick Kossifidis
2008-05-15 19:53 ` Zack Weinberg
2008-05-16 0:50 ` Nick Kossifidis
2008-06-03 21:45 ` Zack Weinberg
2008-06-05 21:50 ` Bob Copeland
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=E1K8GZW-0007vs-I1@hash.localnet \
--to=me@bobcopeland.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mickflemm@gmail.com \
--cc=zackw@panix.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