From: <bogus@does.not.exist.com>
To: ath9k-devel@lists.ath9k.org
Subject: No subject
Date: Thu, 07 Apr 2011 05:55:38 -0000 [thread overview]
Message-ID: <mailman.3.1302620682.6810.ath9k-devel@lists.ath9k.org> (raw)
-------------------------------<BR>
Device Instance Id:<BR>
PCI\VEN_168C&DEV_0030&SUBSYS_3116168C&REV_01\4&492937F&a=
mp;0&00E2<BR>
<BR>
Hardware Ids:<BR>
PCI\VEN_168C&DEV_0030&SUBSYS_3116168C&REV_01<BR>
PCI\VEN_168C&DEV_0030&SUBSYS_3116168C<BR>
PCI\VEN_168C&DEV_0030&CC_028000<BR>
PCI\VEN_168C&DEV_0030&CC_0280<BR>
<BR>
Compatible Ids:<BR>
PCI\VEN_168C&DEV_0030&REV_01<BR>
PCI\VEN_168C&DEV_0030<BR>
PCI\VEN_168C&CC_028000<BR>
PCI\VEN_168C&CC_0280<BR>
PCI\VEN_168C<BR>
PCI\CC_028000<BR>
PCI\CC_0280<BR>
<BR>
Matching Device Id:<BR>
pci\ven_168c&dev_0030&subsys_3116168c<BR>
<BR>
<BR>
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 Window=
s, I booted in to Linux today and found that it is reporting the expecte=
d IDs. Now ath9k works right out of the box, no Vendor ID hacking requir=
ed. 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 thinkin=
g the Windows driver applied a firmware update to the card. Or, the othe=
r card skipped quality checks and has bogus EEPROM data. Any thoughts?<B=
R>
<BR>
0e:00.0 Network controller [0280]: Atheros Communications Inc. AR9300=
Wireless LAN adaptor [168c:0030] (rev 01)<BR>
<BR>
lspci -vvvnn returns<BR>
<BR>
0e:00.0 Network controller [0280]: Atheros Communications Inc. AR9300=
Wireless LAN adaptor [168c:0030] (rev 01)<BR>
Subsystem: Atheros Communicat=
ions Inc. Device [168c:3116]<BR>
Control: I/O+ Mem+ BusMaster+=
SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-=
<BR>
Status: Cap+ 66MHz- UDF- Fast=
B2B- ParErr- DEVSEL=3Dfast >TAbort- <TAbort- <MAbort- >SERR-=
<PERR- INTx-<BR>
Latency: 0, Cache Line Size:=
64 bytes<BR>
Interrupt: pin A routed to=
IRQ 18<BR>
Region 0: Memory at fa000000=
(64-bit, non-prefetchable) [size=3D128K]<BR>
[virtual] Expansion ROM at=
f2000000 [disabled] [size=3D64K]<BR>
Capabilities: <access deni=
ed><BR>
Kernel driver in use: ath9k<B=
R>
Kernel modules: ath9k<BR>
<BR>
<BR>
Hasan R.<BR>
<BR>
-----Original Message-----<BR>
From: Mohammed Shafi [<A HREF=3D"mailto:shafi.ath9k@gmail.com">mailto:sh=
afi.ath9k at gmail.com</A>]<BR>
Sent: Tuesday, April 12, 2011 7:47 AM<BR>
To: Hasan Rashid<BR>
Cc: ath9k-devel at lists.ath9k.org<BR>
Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd<BR>
<BR>
On Mon, Apr 11, 2011 at 11:24 PM, Hasan Rashid <hrashad at avionica.com&=
gt; wrote:<BR>
><BR>
> I have attached the driver load output in dmesg.<BR>
><BR>
> By the way why does AR9382 require Kernel 2.6.36 or higher? Can you=
<BR>
> list the major requirements?<BR>
<BR>
because the hardware code(HAL) will be present from that kernel version=
only.<BR>
><BR>
> Hasan R.<BR>
><BR>
> -----Original Message-----<BR>
> From: ath9k-devel-bounces at lists.ath9k.org<BR>
> [<A HREF=3D"mailto:ath9k-devel-bounces@lists.ath9k.org">mailto:ath9=
k-devel-bounces at lists.ath9k.org</A>] On Behalf Of Peter Stuge<BR>
> Sent: Monday, April 11, 2011 12:20 PM<BR>
> To: ath9k-devel at lists.ath9k.org<BR>
> Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd<BR>
><BR>
> Mohammed Shafi wrote:<BR>
>> to make sure that HT is configured in driver please do this<BR>
>><BR>
>> diff --git a/drivers/net/wireless/ath/ath9k/hw.c<BR>
>> b/drivers/net/wireless/ath/ath9k/hw.c<BR>
>> index 1b5bd13..720a866 100644<BR>
>> --- a/drivers/net/wireless/ath/ath9k/hw.c<BR>
>> +++ b/drivers/net/wireless/ath/ath9k/hw.c<BR>
>> @@ -1855,6 +1855,8 @@ int ath9k_hw_fill_cap_info(struct ath_hw=
*ah)<BR>
>> =A0 =A0 =A0 =A0 else<BR>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 pCap->hw_caps &=3D ~ATH9=
K_HW_CAP_HT;<BR>
>><BR>
>> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 pCap->hw_caps |=3D ATH9K_HW_CA=
P_HT;<BR>
>> +<BR>
><BR>
> The indentation is off, or do you mean to include the added line=
only<BR>
> within the else block? If so, remember to add braces.<BR>
><BR>
><BR>
> //Peter<BR>
> _______________________________________________<BR>
> ath9k-devel mailing list<BR>
> ath9k-devel at lists.ath9k.org<BR>
> <A HREF=3D"https://lists.ath9k.org/mailman/listinfo/ath9k-devel">ht=
tps://lists.ath9k.org/mailman/listinfo/ath9k-devel</A><BR>
><BR>
> This communication contains information that may be confidential=
or<BR>
> 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 communic=
ation is prohibited. If you have received this communication in error,=
please immediately notify the sender by telephone or by electronic mail=
.<BR>
> _______________________________________________<BR>
> ath9k-devel mailing list<BR>
> ath9k-devel at lists.ath9k.org<BR>
> <A HREF=3D"https://lists.ath9k.org/mailman/listinfo/ath9k-devel">ht=
tps://lists.ath9k.org/mailman/listinfo/ath9k-devel</A><BR>
><BR>
><BR>
<BR>
</FONT>
</P>
<!-- Begin Ninja Disclaimer ID 06d1f63c-a7f2-4bdd-9832-359e6e93159e -->
This communication contains information that may be confidential or priv=
ileged. 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 pro=
hibited. If you have received this communication in<BR>error, please imm=
ediately notify the sender by telephone or by electronic mail.
</BODY>
</HTML>
------_=_NextPart_001_01CBF922.E6EB9838--
next reply other threads:[~2011-04-07 5:55 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 5:55 bogus [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-19 18:31 No subject bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-11-19 18:31 bogus
2016-06-13 6:24 bogus
2016-06-13 6:24 bogus
2016-02-09 7:29 bogus
2015-11-16 16:13 bogus
2015-10-12 17:26 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2014-09-13 19:40 bogus
2013-09-15 9:49 bogus
2013-09-15 9:49 bogus
2013-09-15 9:49 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-04-03 10:31 bogus
2013-01-16 21:46 bogus
2013-01-16 21:46 bogus
2012-11-08 9:33 bogus
2012-05-25 15:26 bogus
2012-05-25 15:26 bogus
2012-04-05 7:54 bogus
2012-04-05 7:54 bogus
2012-02-27 5:00 bogus
2012-02-27 5:00 bogus
2012-02-27 5:00 bogus
2012-01-15 8:24 bogus
2011-11-12 14:39 bogus
2011-11-12 14:39 bogus
2011-08-05 3:08 bogus
2011-08-05 3:08 bogus
2011-08-05 3:08 bogus
2011-08-05 3:08 bogus
2011-08-05 3:08 bogus
2011-06-04 23:16 bogus
2011-06-04 23:16 bogus
2011-04-07 5:55 bogus
2011-04-07 5:55 bogus
2011-04-07 5:55 bogus
2011-04-07 5:55 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-12-19 23:59 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-09-24 14:53 bogus
2010-07-23 10:05 bogus
2010-03-25 17:02 bogus
2010-03-25 17:02 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-27 19:01 bogus
2009-02-15 8:49 bogus
2009-01-04 17:33 bogus
2009-01-04 17:33 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-10-14 11:50 bogus
2008-07-28 4:41 bogus
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=mailman.3.1302620682.6810.ath9k-devel@lists.ath9k.org \
--to=bogus@does.not.exist.com \
--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 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).