From: Mike Kershaw <dragorn@kismetwireless.net>
To: G?bor Stefanik <gst@remote-exploit.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ar9170 - Cace Airpcap NX
Date: Wed, 25 Mar 2009 11:43:21 -0400 [thread overview]
Message-ID: <20090325154321.GA4368@drd1813.lan> (raw)
In-Reply-To: <69e28c910903241614s5502a7ffoe85bba0515b8c223@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On Wed, Mar 25, 2009 at 12:14:34AM +0100, G?bor Stefanik wrote:
> On Tue, Mar 24, 2009 at 9:26 PM, Mike Kershaw
> <dragorn@kismetwireless.net> wrote:
> > The Cace Airpcap NX device is an atheros 9170 USB device (sold with custom
> > windows drivers for rfmon in windows).
> >
> > Works fine once the USB device id is added to ar9170, device 0xCACE,0x0300
> >
> > -m
> >
> > --
> > Mike Kershaw/Dragorn <dragorn@kismetwireless.net>
> > GPG Fingerprint: 3546 89DF 3C9D ED80 3381 ?A661 D7B2 8822 738B BDB1
> >
> > Supercollider Programming: The art of debugging your program by
> > letting it crash and looking at what remains.
> >
>
> On a related note, the Cace AirPcap N (PCI/Cardbus/PCIE) is an AR5008,
> with the PCI ID CACE:0023 (PCI/Cardbus)/CACE:0024 (PCIE). Someone with
> an AirPcap N should test if adding this ID to ath9k works.
>
> -G?bor
Works with CACE:0023, don't have a 24 to test with.
-m
--
Mike Kershaw/Dragorn <dragorn@kismetwireless.net>
GPG Fingerprint: 3546 89DF 3C9D ED80 3381 A661 D7B2 8822 738B BDB1
If you can keep your head, while all others around you are loosing theirs,
then you must be the one holding the axe. -- Anonymous
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-03-25 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 20:26 ar9170 - Cace Airpcap NX Mike Kershaw
2009-03-24 20:58 ` [PATCH] ar9170: add Cace Airpcap NX usb_id Christian Lamparter
2009-03-24 23:14 ` ar9170 - Cace Airpcap NX Gábor Stefanik
2009-03-25 15:43 ` Mike Kershaw [this message]
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=20090325154321.GA4368@drd1813.lan \
--to=dragorn@kismetwireless.net \
--cc=gst@remote-exploit.org \
--cc=linux-wireless@vger.kernel.org \
/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).