Return-path: Received: from fk-out-0910.google.com ([209.85.128.190]:28559 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752520AbYEOOlJ (ORCPT ); Thu, 15 May 2008 10:41:09 -0400 Received: by fk-out-0910.google.com with SMTP id 18so332650fkq.5 for ; Thu, 15 May 2008 07:41:07 -0700 (PDT) Message-ID: (sfid-20080515_164114_872147_BF69A300) Date: Thu, 15 May 2008 10:41:07 -0400 From: "Zack Weinberg" To: "Bob Copeland" Subject: Re: Getting ath5k driver working with Thinkpad T61 [168c:1014] Cc: linux-wireless@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 References: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, May 14, 2008 at 3:09 PM, Bob Copeland wrote: > On Wed, May 14, 2008 at 2:45 PM, Zack Weinberg wrote: >> exactly the same thing happens immediately after cold boot with >> nothing else having touched the chip. > > Interesting... can you confirm that madwifi also will not start from a cold > boot? Yes, madwifi will not start from a cold boot. > Perhaps the best thing to do is add printks to ath5k_hw_nic_wakeup and see > where it hangs? It's not hanging. The very first call to ath5k_hw_set_power(ah, AR5K_PM_AWAKE, true, 0); from ath5k_hw_nic_wakeup fails with -EIO, and the driver gives up. zw