Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@panix.com>
To: "Bob Copeland" <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Getting ath5k driver working with Thinkpad T61 [168c:1014]
Date: Thu, 15 May 2008 10:41:07 -0400	[thread overview]
Message-ID: <eb97335b0805150741g252ba49ckbf1b493a46acf762@mail.gmail.com> (raw)
In-Reply-To: <b6c5339f0805141209p4a8b1b2do1cb2ec1c11de07e8@mail.gmail.com>

On Wed, May 14, 2008 at 3:09 PM, Bob Copeland <me@bobcopeland.com> wrote:
> On Wed, May 14, 2008 at 2:45 PM, Zack Weinberg <zackw@panix.com> 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

  reply	other threads:[~2008-05-15 14:41 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 [this message]
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
  -- 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=eb97335b0805150741g252ba49ckbf1b493a46acf762@mail.gmail.com \
    --to=zackw@panix.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.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