On Tue, Jun 3, 2008 at 5:45 PM, Zack Weinberg <zackw@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
