I put another Sparklan card in a Windows XP machine and following are the 
device ids reported by the Atheros driver on Windows. It seems it is reporting 
the correct 0x168c, and 0x0030. 

>From Windows XP Device Manager
-------------------------------
Device Instance Id:
PCI\VEN_168C&DEV_0030&SUBSYS_3116168C&REV_01\4&492937F&0&00E2

Hardware Ids:
PCI\VEN_168C&DEV_0030&SUBSYS_3116168C&REV_01
PCI\VEN_168C&DEV_0030&SUBSYS_3116168C
PCI\VEN_168C&DEV_0030&CC_028000
PCI\VEN_168C&DEV_0030&CC_0280

Compatible Ids:
PCI\VEN_168C&DEV_0030&REV_01
PCI\VEN_168C&DEV_0030
PCI\VEN_168C&CC_028000
PCI\VEN_168C&CC_0280
PCI\VEN_168C
PCI\CC_028000
PCI\CC_0280

Matching Device Id:
pci\ven_168c&dev_0030&subsys_3116168c


Here is the interesting bit, when I first hooked this card I booted my machine 
in Ubuntu I saw the same 168c:ABCD. After using it under Windows, I booted in 
to Linux today and found that it is reporting the expected IDs. Now ath9k works 
right out of the box, no Vendor ID hacking required. I am using it as station 
right now. The other card is in a different machine. I will try to swap the 
cards to verify my theory. I am thinking the Windows driver applied a firmware 
update to the card. Or, the other card skipped quality checks and has bogus 
EEPROM data. Any thoughts?

0e:00.0 Network controller [0280]: Atheros Communications Inc. AR9300 Wireless 
LAN adaptor [168c:0030] (rev 01)

lspci -vvvnn returns

0e:00.0 Network controller [0280]: Atheros Communications Inc. AR9300 Wireless 
LAN adaptor [168c:0030] (rev 01)
        Subsystem: Atheros Communications Inc. Device [168c:3116]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at fa000000 (64-bit, non-prefetchable) [size=128K]
        [virtual] Expansion ROM at f2000000 [disabled] [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: ath9k
        Kernel modules: ath9k


Hasan R.

-----Original Message-----
From: Mohammed Shafi [mailto:shafi.at...@gmail.com] 
Sent: Tuesday, April 12, 2011 7:47 AM
To: Hasan Rashid
Cc: ath9k-devel@lists.ath9k.org
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

On Mon, Apr 11, 2011 at 11:24 PM, Hasan Rashid <hras...@avionica.com> wrote:
>
> I have attached the driver load output in dmesg.
>
> By the way why does AR9382 require Kernel 2.6.36 or higher? Can you 
> list the major requirements?

because the hardware code(HAL) will be present from that kernel version only.
>
> Hasan R.
>
> -----Original Message-----
> From: ath9k-devel-boun...@lists.ath9k.org
> [mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of Peter Stuge
> Sent: Monday, April 11, 2011 12:20 PM
> To: ath9k-devel@lists.ath9k.org
> Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd
>
> Mohammed Shafi wrote:
>> to make sure that HT is configured in driver please do this
>>
>> diff --git a/drivers/net/wireless/ath/ath9k/hw.c
>> b/drivers/net/wireless/ath/ath9k/hw.c
>> index 1b5bd13..720a866 100644
>> --- a/drivers/net/wireless/ath/ath9k/hw.c
>> +++ b/drivers/net/wireless/ath/ath9k/hw.c
>> @@ -1855,6 +1855,8 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah)
>>         else
>>                 pCap->hw_caps &= ~ATH9K_HW_CAP_HT;
>>
>> +               pCap->hw_caps |= ATH9K_HW_CAP_HT;
>> +
>
> The indentation is off, or do you mean to include the added line only 
> within the else block? If so, remember to add braces.
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
> This communication contains information that may be confidential or 
> privileged. The information is solely intended for the use of the addressee. 
> If you are not the intended recipient, be advised that any disclosure, copy, 
> distribution, or use of the contents of this communication is prohibited. If 
> you have received this communication in error, please immediately notify the 
> sender by telephone or by electronic mail.
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>


This communication contains information that may be confidential or privileged. 
The information is solely intended for the use of the addressee. If you are not 
the intended recipient, be advised that any disclosure, copy, distribution, or 
use of the contents of this communication is prohibited. If you have received 
this communication in
error, please immediately notify the sender by telephone or by electronic mail.
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to