mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: William Thompson <wt@electro-mechanical.com>
Cc: linux-kernel@vger.kernel.org, ath5k-devel <ath5k-devel@venema.h4ckr.net>
Subject: Re: 3com 3crxjk10075 with ath5k driver
Date: Tue, 9 Jun 2009 16:39:12 -0400	[thread overview]
Message-ID: <b6c5339f0906091339j3784c36bxe888af16272fbcde@mail.gmail.com> (raw)
In-Reply-To: <20090609195100.GY19203@electro-mechanical.com>

[CCed ath5k-devel]

On Tue, Jun 9, 2009 at 3:51 PM, William
Thompson<wt@electro-mechanical.com> wrote:
> This card has the "xjack" antennae which is supposed to disable the radio (I
> thought it was in hardware, but it's not) when it is not extended.  The
> madwifi driver (Last time I actually used this card with it) did disable the
> radio (Or refused packets, not sure which).

Huh, I wonder how that works.  Is disabling the radio an advertised feature?
i.e. as opposed to just not working because the antenna is in?

> The kernel ath5k driver (last tested 2.6.29.4) will work regardless if the
> antannae is in or out.

I suppose it could be asserting something on rfkill gpios; ath5k hasn't had
real rfkill support yet.  Anyone else know about these devices?

-- 
Bob Copeland %% www.bobcopeland.com

  reply	other threads:[~2009-06-09 20:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 19:51 William Thompson
2009-06-09 20:39 ` Bob Copeland [this message]
2009-06-10 11:23   ` William Thompson
2009-06-10 11:34     ` Bob Copeland
2009-06-10 11:54       ` William Thompson
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=b6c5339f0906091339j3784c36bxe888af16272fbcde@mail.gmail.com \
    --to=me@bobcopeland.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wt@electro-mechanical.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

all inboxes | Powered by JetHome®