From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] trouble with DWA-552 and ath9k
Date: Thu, 25 Feb 2010 13:31:38 -0500 [thread overview]
Message-ID: <1267122698.7508.20.camel@mj> (raw)
In-Reply-To: <1267035256.9225.37.camel@mj>
On Wed, 2010-02-24 at 13:14 -0500, Pavel Roskin wrote:
> Sorry, I found it:
> https://lists.ath9k.org/pipermail/ath9k-devel/2010-January/003019.html
>
> Looking at it now.
I have bought DWA-552 from Newegg. It's revision A2. The chip is
marked as AR9223.
lspci should that it's exactly the same device as yours:
02:01.0 Network controller [0280]: Atheros Communications Inc. AR922X
Wireless Network Adapter [168c:0029] (rev 01)
Subsystem: D-Link System Inc Device [1186:3a7a]
Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 18
Memory at fe3f0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Kernel driver in use: ath9k
Kernel modules: ath9k
ath9h identifies the device as:
phy3: Atheros AR9280 Rev:2 mem=0xffffc90010260000, irq=18
I cannot reproduce your problem. Everything is working just fine.
I checked what is read from the register 0x7000. It's always 0x00000000
or 0x00000002 and never 0xffffffff. I assume your card has some
hardware issue.
But the way, revision A2 doesn't just have another chip. It looks very
different from the revision A1. It's smaller and comes with an
additional low-profile bracket. Antennas are closer to each other. The
picture on the box shows it clearly. D-Link must be getting really low
on model numbers if they are reusing the same number for a substantially
different product.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-02-25 18:31 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:43 [ath9k-devel] trouble with DWA-552 and ath9k Brian Walker
2009-12-18 3:12 ` Sujith
2009-12-18 3:51 ` Brian Walker
2009-12-18 4:44 ` Sujith
2009-12-18 11:55 ` Brian Walker
2009-12-19 3:05 ` Brian Walker
2009-12-22 4:58 ` Sujith
[not found] ` <4B30D348.3080600@charter.net>
2009-12-22 18:39 ` Brian Walker
2009-12-28 19:22 ` Brian Walker
2009-12-28 20:49 ` Pavel Roskin
2009-12-28 21:06 ` Brian Walker
2009-12-28 21:28 ` Pavel Roskin
2009-12-28 22:54 ` Brian Walker
2009-12-29 15:02 ` Pavel Roskin
2009-12-29 23:23 ` Brian Walker
2009-12-30 6:16 ` Pavel Roskin
2010-01-05 16:49 ` Brian Walker
2010-01-08 4:34 ` Sujith
2010-01-09 15:14 ` Brian Walker
2010-01-09 15:38 ` Pavel Roskin
2010-01-09 19:33 ` Brian Walker
2010-01-10 5:12 ` Sujith
2010-01-11 18:42 ` Brian Walker
2010-01-13 1:18 ` Brian Walker
2010-01-13 8:04 ` Sujith
2010-01-13 15:35 ` Pavel Roskin
2010-01-13 17:28 ` Pavel Roskin
2010-01-14 2:58 ` Brian Walker
2010-01-14 6:15 ` Pavel Roskin
2010-01-14 11:51 ` Brian Walker
2010-01-14 23:13 ` Pavel Roskin
2010-01-15 5:40 ` Pavel Roskin
2010-01-16 16:27 ` Brian Walker
2010-01-20 23:03 ` Pavel Roskin
2010-01-25 18:47 ` Brian Walker
2010-01-25 19:34 ` Pavel Roskin
2010-01-27 0:52 ` Brian Walker
2010-01-27 23:13 ` Pavel Roskin
2010-01-28 0:36 ` Brian Walker
2010-02-05 19:13 ` Brian Walker
2010-02-05 19:34 ` Pavel Roskin
2010-02-06 0:56 ` Brian Walker
2010-02-06 5:20 ` Pavel Roskin
2010-02-10 1:00 ` Brian Walker
2010-02-10 19:24 ` Pavel Roskin
2010-02-10 19:57 ` Brian Walker
2010-02-20 3:00 ` Brian Walker
2010-02-23 21:30 ` Pavel Roskin
2010-02-24 1:21 ` Brian Walker
2010-02-24 6:09 ` [ath9k-devel] hostapd-0.7-1 failed work with ath9k Zhang Yanfei-B21500
2010-02-24 6:42 ` Pavel Roskin
2010-03-02 10:20 ` yingqiang Ma
2010-03-03 2:01 ` Zhang Yanfei-B21500
2010-02-24 6:40 ` [ath9k-devel] trouble with DWA-552 and ath9k Pavel Roskin
2010-02-24 13:21 ` Brian Walker
2010-02-24 18:09 ` Pavel Roskin
2010-02-24 18:14 ` Pavel Roskin
2010-02-25 18:31 ` Pavel Roskin [this message]
2010-02-25 20:34 ` Peter Stuge
2010-02-26 1:10 ` Brian Walker
2010-02-26 23:35 ` Pavel Roskin
2010-03-02 0:48 ` Brian Walker
2010-03-03 4:31 ` Pavel Roskin
2010-03-02 0:55 ` Brian Walker
2010-03-03 4:33 ` Pavel Roskin
2010-03-08 2:20 ` Brian Walker
-- strict thread matches above, loose matches on Subject: below --
2009-12-17 19:52 Brian Walker
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=1267122698.7508.20.camel@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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 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.