[ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2013-03-27 Thread Steffen Dettmer
Hi, some time ago there was a thread "Sparklan WPEA-121N AR9382 168c:abcd" about the issue that the mentioned device was erroneously reported as device ID 0xabcd. There were EEPROM issues assumed and BIOS issues reported that could cause this effect (by resetting the PCI bus at system power on)

Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd

2013-03-28 Thread Steffen Dettmer
Hi all, thanks for all your replies. Let me tell my findings just in case it helps. * adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] wrote: > The general consensus at work is - BIOSes are buggy and don't > necessarily reset the PCI bus correctly. > > So either you can do your own PCI bus

[ath9k-devel] Interpreting "link quality" of cards driven by ath9k to estimate usable bandwidth?

2013-04-03 Thread Steffen Dettmer
Hi, man iwconfig tells, "Link quality... depends totally on the driver and hardware". I would like to know how to interpret the value for WPEA-127N driven by ath9k - ideally to have a base value for estimation of "useable bandwidth" (i.e. how much data could be sent and received per time). Is

Re: [ath9k-devel] Interpreting "link quality" of cards driven by ath9k to estimate usable bandwidth?

2013-04-05 Thread Steffen Dettmer
Hi, thanks a lot for your helpful mail. I made several tests and good progress, thanks to you :) * Holger Schurig [mailto:holgerschu...@gmail.com] wrote: > Hi, I wouldn't use "iwconfig" and link quality. > > "iwconfig" is outdated and virtually unmaintained since years. Ohh, good to know... it i