LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Bob Copeland" <me@bobcopeland.com>
To: "Jiri Slaby" <jirislaby@gmail.com>,
	"Tino Keitel" <tino.keitel@gmx.de>,
	linux-kernel@vger.kernel.org, ath5k-devel@lists.ath5k.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFT 1/1] single_chip test
Date: Wed, 6 Feb 2008 10:46:39 -0500	[thread overview]
Message-ID: <b6c5339f0802060746m3a5f87edj4465797564430292@mail.gmail.com> (raw)
In-Reply-To: <20080206150043.GA6921@nineveh.local>

> > We failed to resume after a hardware reset here for a whole second. Is there any
> > version of ath5k which worked for you (is this a regression)?
>
> I cannot speak for Tino, but my ath5k never worked in MacBook -- it
> failed the same way, and I believe the hardware was the same.  My
> understanding was that it was a known bug with PCIE devices, but I got
> that out of reading list archives.

Nick Kossifidis and I are in the process of debugging this -- we
determined that AR5K_RESET_CTL_PCI hangs the card in hw_nic_wakeup.
It doesn't look like there is any general support for 5424 cards yet.
Thread is at:

    http://marc.info/?l=linux-wireless&m=120179743111458

-Bob

  reply	other threads:[~2008-02-06 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 22:57 ath5k failure with 2.6.24-git14 Tino Keitel
2008-02-06  9:41 ` Andrew Morton
2008-02-06 10:42   ` [RFT 1/1] single_chip test Jiri Slaby
2008-02-06 10:48     ` Andreas Schwab
2008-02-06 10:53       ` Jiri Slaby
2008-02-06 15:00     ` Joseph Fannin
2008-02-06 15:46       ` Bob Copeland [this message]
2008-02-07 21:25         ` Tino Keitel
2008-02-07 21:51           ` Jiri Slaby
2008-02-08  7:28             ` Tino Keitel
2008-02-06 15:37   ` ath5k failure with 2.6.24-git14 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=b6c5339f0802060746m3a5f87edj4465797564430292@mail.gmail.com \
    --to=me@bobcopeland.com \
    --cc=akpm@linux-foundation.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tino.keitel@gmx.de \
    --subject='Re: [RFT 1/1] single_chip test' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).