From: Richard Zidlicky <rz@linux-m68k.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: kernel crashes, 2.6.30, rt2x00, ath5k, ieee80211_get_*_rate, automatic rate control
Date: Thu, 25 Jun 2009 10:36:36 +0200 [thread overview]
Message-ID: <20090625083636.GA6323@linux-m68k.org> (raw)
In-Reply-To: <20090623202541.GA3635@hash.localnet>
On Tue, Jun 23, 2009 at 04:25:41PM -0400, Bob Copeland wrote:
>
> The patch should already be on the way to stable, but I'll check on it.
thanks, you certainly have my vote that it should get into 2.6.30.*
On an unrelated note, the ath5k device is in a netbook with an wifi LED and
Fn-F2 hotkey to toggle wlan.
The hotkey works, the LED not. What do I need to make the LED working on the
device?
Also, while the hotkey works how do query the current on/off status of it
in Linux?
Richard
next prev parent reply other threads:[~2009-06-25 14:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 13:49 kernel crashes, 2.6.30, rt2x00, ath5k, ieee80211_get_*_rate, automatic rate control Richard Zidlicky
2009-06-21 18:04 ` Bob Copeland
2009-06-21 20:38 ` Richard Zidlicky
2009-06-22 20:15 ` Richard Zidlicky
2009-06-23 17:46 ` Richard Zidlicky
2009-06-23 20:25 ` Bob Copeland
2009-06-25 8:36 ` Richard Zidlicky [this message]
2009-07-05 12:31 ` Bob Copeland
2009-09-28 22:23 ` ath5k, wifi enable hotkeys Richard Zidlicky
2009-10-09 14:39 ` 2.6.31.[12] ath5k regression Richard Zidlicky
2009-10-10 12:58 ` Bob Copeland
2009-10-10 13:31 ` Bob Copeland
2009-10-11 12:26 ` Richard Zidlicky
2009-10-11 13:30 ` Bob Copeland
2009-10-11 22:00 ` Richard Zidlicky
2009-10-11 22:23 ` Bob Copeland
2009-10-12 20:23 ` Richard Zidlicky
2009-10-12 23:54 ` Bob Copeland
2009-10-13 19:37 ` Richard Zidlicky
2009-12-06 9:49 ` Richard Zidlicky
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=20090625083636.GA6323@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.