Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
true its an already reported platform specific issue, usually they use this id for emulation testing. as a workaround this PID has to be added to support this card in that specific platform On Mon, Oct 10, 2011 at 8:06 PM, Adrian Chadd adr...@freebsd.org wrote: .. sounds like another PCI bus setup/reset problem. Sigh. :) Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- shafi ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
Hi!
I want to use an AR9380 mini pci-e module on kirkwood. under x86 the
module
works fine and appears as product-id 0x0030, on kirkwood the same
module shows
up as product-id 0xabcd.
Anyone knows possible reasons for this to happen?
(First I suspected there could be an PCI expansion ROM executed by
the x86 BIOS,
that doesn't seem to be that case.)
Any hints welcome :)
You could use sth like that in your setup.
---
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/pci.c
2011-05-31 21:02:34.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
2011-06-06 12:58:57.578412992 +0200
@@ -30,6 +30,7 @@
{ PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI */
{ PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
{ PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E AR9300 */
+ { PCI_VDEVICE(ATHEROS, 0xABCD) }, /* PCI-E AR9380 */
{ PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E AR9485 */
{ 0 }
};
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 13:00:12.568412970 +0200
@@ -653,6 +653,7 @@
case AR2427_DEVID_PCIE:
case AR9300_DEVID_PCIE:
case AR9300_DEVID_AR9485_PCIE:
+ case AR9300_DEVID_AR9380_PCIE:
case AR9300_DEVID_AR9330:
case AR9300_DEVID_AR9340:
break;
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:57.578412992 +0200
@@ -44,6 +44,7 @@
#define AR9287_DEVID_PCIE 0x002e
#define AR9300_DEVID_PCIE 0x0030
#define AR9300_DEVID_AR93400x0031
+#define AR9300_DEVID_AR9380_PCIE 0xabcd
#define AR9300_DEVID_AR9485_PCIE 0x0032
#define AR9300_DEVID_AR93300x0035
---
It has worked for me on kirkwood platform.
Wojtek
Cheers
Daniel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
I've seen this happen on legacy nics: * when the nic had failed (an ar9227 nic); * when someone changed motherboards (various ar5212 era nics). The latter is something I'm currently digging into. There seems to be some subtle PCI reset/setup stuff going on (eg by changing some PCI parameters in the BIOS - I'm still trying to get some more accurate info from the users in question) which really need to be properly debugged and documented. I really hate seeing things like this happen. I have no idea what other subtle implications there are :( Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
Sure, that's what I did already to make it work at least a bit, but run into DMA
problems once there was any serious traffic (using Kernel 2.6.39 and
compat-wireless 2011-06-20)
Kernel 3.0.4 with compat-wireless 2011-10-05 seems to work quite nice, at least
for now... I'll continue testing that in the next days.
On 10/11/2011 09:58 AM, Wojciech Dubowik wrote:
Hi!
I want to use an AR9380 mini pci-e module on kirkwood. under x86 the
module
works fine and appears as product-id 0x0030, on kirkwood the same
module shows
up as product-id 0xabcd.
Anyone knows possible reasons for this to happen?
(First I suspected there could be an PCI expansion ROM executed by
the x86 BIOS,
that doesn't seem to be that case.)
Any hints welcome :)
You could use sth like that in your setup.
---
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/pci.c
2011-05-31 21:02:34.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
2011-06-06 12:58:57.578412992 +0200
@@ -30,6 +30,7 @@
{ PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI */
{ PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
{ PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E AR9300 */
+ { PCI_VDEVICE(ATHEROS, 0xABCD) }, /* PCI-E AR9380 */
{ PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E AR9485 */
{ 0 }
};
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 13:00:12.568412970 +0200
@@ -653,6 +653,7 @@
case AR2427_DEVID_PCIE:
case AR9300_DEVID_PCIE:
case AR9300_DEVID_AR9485_PCIE:
+ case AR9300_DEVID_AR9380_PCIE:
case AR9300_DEVID_AR9330:
case AR9300_DEVID_AR9340:
break;
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:57.578412992 +0200
@@ -44,6 +44,7 @@
#define AR9287_DEVID_PCIE0x002e
#define AR9300_DEVID_PCIE0x0030
#define AR9300_DEVID_AR9340 0x0031
+#define AR9300_DEVID_AR9380_PCIE 0xabcd
#define AR9300_DEVID_AR9485_PCIE 0x0032
#define AR9300_DEVID_AR9330 0x0035
---
It has worked for me on kirkwood platform.
Wojtek
Cheers
Daniel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
On Tue, Oct 11, 2011 at 6:06 PM, Daniel Golle dgo...@allnet.de wrote:
Sure, that's what I did already to make it work at least a bit, but run into
DMA
problems once there was any serious traffic (using Kernel 2.6.39 and
compat-wireless 2011-06-20)
Kernel 3.0.4 with compat-wireless 2011-10-05 seems to work quite nice, at
least
for now... I'll continue testing that in the next days.
please try to see the DMA problems are fixed in latest compat
http://linuxwireless.org/en/users/Download#Where_to_download_bleeding_edge
On 10/11/2011 09:58 AM, Wojciech Dubowik wrote:
Hi!
I want to use an AR9380 mini pci-e module on kirkwood. under x86 the
module
works fine and appears as product-id 0x0030, on kirkwood the same
module shows
up as product-id 0xabcd.
Anyone knows possible reasons for this to happen?
(First I suspected there could be an PCI expansion ROM executed by
the x86 BIOS,
that doesn't seem to be that case.)
Any hints welcome :)
You could use sth like that in your setup.
---
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/pci.c
2011-05-31 21:02:34.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/pci.c
2011-06-06 12:58:57.578412992 +0200
@@ -30,6 +30,7 @@
{ PCI_VDEVICE(ATHEROS, 0x002D) }, /* PCI */
{ PCI_VDEVICE(ATHEROS, 0x002E) }, /* PCI-E */
{ PCI_VDEVICE(ATHEROS, 0x0030) }, /* PCI-E AR9300 */
+ { PCI_VDEVICE(ATHEROS, 0xABCD) }, /* PCI-E AR9380 */
{ PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E AR9485 */
{ 0 }
};
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.c
2011-06-06 13:00:12.568412970 +0200
@@ -653,6 +653,7 @@
case AR2427_DEVID_PCIE:
case AR9300_DEVID_PCIE:
case AR9300_DEVID_AR9485_PCIE:
+ case AR9300_DEVID_AR9380_PCIE:
case AR9300_DEVID_AR9330:
case AR9300_DEVID_AR9340:
break;
Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
===
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:50.0 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath9k/hw.h
2011-06-06 12:58:57.578412992 +0200
@@ -44,6 +44,7 @@
#define AR9287_DEVID_PCIE 0x002e
#define AR9300_DEVID_PCIE 0x0030
#define AR9300_DEVID_AR9340 0x0031
+#define AR9300_DEVID_AR9380_PCIE 0xabcd
#define AR9300_DEVID_AR9485_PCIE 0x0032
#define AR9300_DEVID_AR9330 0x0035
---
It has worked for me on kirkwood platform.
Wojtek
Cheers
Daniel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
--
shafi
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
[ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
Hi! I want to use an AR9380 mini pci-e module on kirkwood. under x86 the module works fine and appears as product-id 0x0030, on kirkwood the same module shows up as product-id 0xabcd. Anyone knows possible reasons for this to happen? (First I suspected there could be an PCI expansion ROM executed by the x86 BIOS, that doesn't seem to be that case.) Any hints welcome :) Cheers Daniel ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Re: [ath9k-devel] AR9380 appears as product id 0xABCD instead of 0x0030
.. sounds like another PCI bus setup/reset problem. Sigh. :) Adrian ___ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
