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
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
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
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
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
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
.. 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
