From: "Bob Copeland" <me@bobcopeland.com>
To: "Zack Weinberg" <zackw@panix.com>
Cc: linux-wireless@vger.kernel.org, "Nick Kossifidis" <mickflemm@gmail.com>
Subject: Re: Getting ath5k driver working with Thinkpad T61 [168c:1014]
Date: Thu, 15 May 2008 16:44:07 -0400 [thread overview]
Message-ID: <b6c5339f0805151344m2832d8e0s2d2b62338e2f8d5b@mail.gmail.com> (raw)
In-Reply-To: <eb97335b0805150953m5d5fd39bm896b7a108a1909c@mail.gmail.com>
On Thu, May 15, 2008 at 12:53 PM, Zack Weinberg <zackw@panix.com> wrote:
>> Unless anyone
>> else has ideas, I would suggest capturing a trace using mmiotrace and
>> ndiswrapper to see what is going on. Someone on ath5k-devel list
>> might have a better idea.
>
> I don't know how to do that, can you point me at instructions?
There are some instructions over here, but they are a little out of date:
http://madwifi.org/wiki/DevDocs/MadwifiTrace
I think believe the info from the nouveau link below is more recent.
It's changed a lot even since the last time I ran it a month or two
ago, so you may have to do a little research. "Built-in mmiotrace"
seems to be where it's going lately.
http://nouveau.freedesktop.org/wiki/MmioTrace
First step would be to get your card working under ndiswrapper, I guess.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-05-15 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 15:24 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=b6c5339f0805151344m2832d8e0s2d2b62338e2f8d5b@mail.gmail.com \
--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