From: "Bob Copeland" <me@bobcopeland.com>
To: "Zack Weinberg" <zackw@panix.com>
Cc: "Nick Kossifidis" <mickflemm@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Getting ath5k driver working with Thinkpad T61 [168c:1014]
Date: Thu, 5 Jun 2008 17:50:08 -0400 [thread overview]
Message-ID: <b6c5339f0806051450i47b5d874y86398cec61675ce6@mail.gmail.com> (raw)
In-Reply-To: <eb97335b0806031445l4f2061ccue65ae54ef5a540bf@mail.gmail.com>
On Tue, Jun 3, 2008 at 5:45 PM, Zack Weinberg <zackw@panix.com> wrote:
> I'm sorry to have taken so long to get back to y'all. It turns out I
> was wrong about madwifi, it does work with this chipset.
Great!
> Since it works now with madwifi, I am attaching mmiotrace runs for
> ath5k (latest compat-wireless driver, which still doesn't work) and
> madwifi.
Any changes in the dmesg output when you use ath5k? I looked very briefly and
didn't see the usual symptom of a locked up card (reads of 0xffffffff), but it
also looks like there is only .08 seconds covered by the trace. Could you try
another trace for a bit longer?
> Please let me know if you still want to see traces for the
> windows driver. (The madwifi trace also includes a successful "iwlist
> wlan0 scan" operation; the ath5k trace obviously does not.)
Probably not necessary -- the madwifi trace looks fine.
Thanks!
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2008-06-05 21:50 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
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 [this message]
-- 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=b6c5339f0806051450i47b5d874y86398cec61675ce6@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