Mohammed Shafi wrote: > > Is this a serious proposal from Atheros, or just your attempt at > > a quick fix? > > No! its purely a personal idea (am completely responsible for the > mistake),and I will take a look at it carefully to fix this.
Sorry, I didn't mean that you made a mistake, just that the suggestion probably would not get us closer to the actual issue. Bus level issues are indeed difficult. :\ > > A device having an unexpected PCI id means that something is really > > wrong in the device or on the bus, and the solution is rarely to > > pretend that it didn't happen.] > > Yeah I can see that, hoping that I may get a correct Device ID from > the reporter. I dont think 'abcd' is a proper vendor id. Yes, it's easy to spot. The question is how we can find out *why* this happened, so that this error case can be prevented. > > Since this card should work fine in principle, maybe it's some issue > > with missing, or wrong, firmware stored on the Linux system. > > AR9382 does not seems to have firmware Aha! That's only for the USB devices maybe. I don't know much detail for these latest devices. > and you have any idea what might went wrong. Sorry, I don't understand what you mean here. > Also why its detected as Ethernet Controller rather than > Network controller. This string comes from the pciutils package and could easily have changed. Better look at the numerical device class code, which is what is read from hardware. But I expect that when one thing in config space (device id) is bogus then the rest of config space is also quite possibly bogus, for the same reason, whatever it is. //Peter _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
