linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Looking for 3x3 Atheros NICs using ath9k driver.
Date: Fri, 06 May 2011 15:53:56 -0700	[thread overview]
Message-ID: <4DC47C04.1080604@candelatech.com> (raw)
In-Reply-To: <4DC17DAE.9020808@candelatech.com>

On 05/04/2011 09:24 AM, Ben Greear wrote:
> On 05/04/2011 09:16 AM, Adrian Chadd wrote:
>> On 4 May 2011 02:00, Ben Greear<greearb@candelatech.com> wrote:
>>
>>> Here's the lspci for the SR71-A that doesn't work with ath9k:
>>>
>>> 03:00.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless
>>> Network Adapter (rev 01)
>>> Subsystem: Atheros Communications Inc. Device ee1c
>>
>> ... ee1c? Err, that isn't right. Not by a very, very long shot.
>>
>> What board are you putting this into?
>>
>>> From FreeBSD on a RSPRO (ar71xx mips):
>>
>> ath0@pci0:0:17:0: class=0x028000 card=0x40820777 chip=0x0027168c
>> rev=0x01 hdr=0x00
>> vendor = 'Atheros Communications Inc.'
>> class = network
>>
>> That definitely, positively is the same AC1A revision that you have.
>> It even does 11n(ag) too. Honest. I've seen it. :-)
>>
>> This and the previous AR93xx "0xabcd" device id post is starting to
>> sound a lot like something's not waking up the PCI bus and/or chip
>> "right" in order to get the PCI vendor id init'ed from the EEPROM..
>
> Well, I put in one NIC, it works fine, I put in the other, and it doesn't.
>
> Same system, reproducible on other systems from same manufacturer
> (Lanner, LEC 2010E).
>
> Haven't tried it on a totally different motherboard. I'll send you this
> broken NIC if you want...I'm too tight on time to hack on it now...

So, you were right.  I put this NIC in another system (VIA C3) and it comes up
as AR9160 and loads ath9k driver just fine.

00:0c.0 Network controller: Atheros Communications Inc. AR9160 802.11abgn Wireless PCI Adapter (rev 01)
	Subsystem: Device 0777:4082
	Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 18
	Memory at f6000000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
	Kernel driver in use: ath9k
	Kernel modules: ath9k

Thanks,
Ben

>
> Ben
>
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2011-05-06 22:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 20:51 Looking for 3x3 Atheros NICs using ath9k driver Ben Greear
2011-05-02 21:35 ` Brian Prodoehl
2011-05-02 22:00 ` Pat Erley
2011-05-02 22:19   ` Ben Greear
2011-05-03  6:13 ` Adrian Chadd
2011-05-03  9:39   ` Roberto Riggio
2011-05-03 10:39     ` Adrian Chadd
2011-05-03 16:36   ` Ben Greear
2011-05-03 18:00   ` Ben Greear
2011-05-04 16:16     ` Adrian Chadd
2011-05-04 16:24       ` Ben Greear
2011-05-06 22:53         ` Ben Greear [this message]
2011-05-07  2:31           ` Adrian Chadd
2011-05-07  3:42             ` Ben Greear
2011-05-07  4:56               ` Adrian Chadd
2011-05-09 19:05           ` Ben Greear
2011-05-10  2:21             ` Adrian Chadd
2011-05-10 20:51               ` Ben Greear
2011-05-11  2:11                 ` Adrian Chadd
2011-05-12 18:18                 ` Ben Greear

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=4DC47C04.1080604@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian@freebsd.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).