All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Thompson <wt@electro-mechanical.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: linux-kernel@vger.kernel.org, ath5k-devel <ath5k-devel@venema.h4ckr.net>
Subject: Re: 3com 3crxjk10075 with ath5k driver
Date: Wed, 10 Jun 2009 07:54:32 -0400	[thread overview]
Message-ID: <20090610115432.GC19203@electro-mechanical.com> (raw)
In-Reply-To: <20090610113406.GE19635@hash.localnet>

On Wed, Jun 10, 2009 at 07:34:06AM -0400, Bob Copeland wrote:
> On Wed, Jun 10, 2009 at 07:23:57AM -0400, William Thompson wrote:
> > > I suppose it could be asserting something on rfkill gpios; ath5k hasn't had
> > > real rfkill support yet.  Anyone else know about these devices?
> > 
> > It's possible.  The LED on it goes off when it's pushed in.  Which reminds
> > me, I don't think the ath5k driver allows the LED to blink when it's
> > transmitting/receiving, it just stays on.
> 
> Can you try latest wireless-testing?  There's an rfkill patch for
> ath5k in it.  URL is:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git

Unfortunately, I don't know how to use git.

> As for LEDs, there's a patch in kernel bugzilla.  I don't have a link handy
> but you can check the ath5k-devel archives from a week or two ago, let
> me know if you can't find it.

I'll see.

  reply	other threads:[~2009-06-10 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 19:51 3com 3crxjk10075 with ath5k driver William Thompson
2009-06-09 20:39 ` Bob Copeland
2009-06-10 11:23   ` William Thompson
2009-06-10 11:34     ` Bob Copeland
2009-06-10 11:54       ` William Thompson [this message]
2009-06-10 12:07         ` Bob Copeland
2009-06-11 15:25           ` William Thompson
2009-06-11 17:41             ` Bob Copeland
2009-06-11 18:33               ` William Thompson
2009-06-11 18:40                 ` [ath5k-devel] " 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=20090610115432.GC19203@electro-mechanical.com \
    --to=wt@electro-mechanical.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=linux-kernel@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 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.