linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-wireless@vger.kernel.org
Subject: ath5k, wifi enable hotkeys
Date: Tue, 29 Sep 2009 00:23:49 +0200	[thread overview]
Message-ID: <20090928222349.GA2416@linux-m68k.org> (raw)
In-Reply-To: <20090705123105.GE2132@hash.localnet>

On Sun, Jul 05, 2009 at 08:31:05AM -0400, Bob Copeland wrote:

Hi,


> Try latest wireless-testing or 2.6.31-rc1; there may already be a fix
> for your hardware thanks to recently added rfkill support.

got around to give 2.6.30* more testing. LED now works nicely but that is about the
only thing that works.

Tried computers linked in Ad-Hoc mode with WEP. 2.6.30 and 2.6.31.1 work nicely
on the other end.

On the ath5k end it seems like 2.6.31 choked after resume from suspend or when interface 
was reconfigured. 

2.6.31.1 does not work at all on this netbook. LED indicates activity but network does
not get associated. "iwlist scan" does display available networks.

After having tried 2.6.31.1 I have to cold-boot 2.6.30.x to get the ath5k working again,
simple reboot does not do it.

> 
> > Also, while the hotkey works how do query the current on/off status of it 
> > in Linux?
> 
> There's the /dev/rfkill device (see http://git.sipsolutions.net/rfkill.git)
> and I believe there are files under /sys/ as well which show the state but
> I don't have the details handy (/sys/class/rfkill/xxx/state?).

has that been merged into 2.6.31* ? 

The /sys/.../rfkill files are there but could not figure out anything that changes 
when hitting the hotkey.

Besides, I would think the LED will indicate rfkill status?

Richard

  reply	other threads:[~2009-09-28 22:26 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
2009-07-05 12:31         ` Bob Copeland
2009-09-28 22:23           ` Richard Zidlicky [this message]
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=20090928222349.GA2416@linux-m68k.org \
    --to=rz@linux-m68k.org \
    --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;
as well as URLs for NNTP newsgroup(s).