Hello Michał
yes, I checked the actual performance via netcat, scp and rsync. I'll report back once I have tested against another AP. Michael On 10/27/2015 07:22 AM, Michal Kazior wrote: > On 26 October 2015 at 22:18, Michael Krupp <[email protected]> wrote: >> Hello, >> >> >> I managed to get it (sort of) working with the eeprom extracted from the >> windows >> driversand thefirmware from kvalo's ath10k-repo on GitHub.See more details >> below. >> >> Unfortunately I only get a bandwidth of about 2Mb/s connected to a 54Mb/s >> AP.Is >> this a known limitation to ath10k right now, or may there be a way to get it >> working at full speed? >> >> >> Also, thank You Michał for pointing me the right direction and helping make >> it >> usable, at least. >> >> -- > [...] >> # iwconfig wlp7s0: >> >> wlp7s0 IEEE 802.11abgn ESSID:"[REMOVED]" >> Mode:Managed Frequency:2.457 GHz Access Point: 00:24:FE:A8:2C:55 >> Bit Rate=1 Mb/s Tx-Power=20 dBm >> Retry short limit:7 RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:on >> Link Quality=69/70 Signal level=-41 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:32 Missed beacon:0 > > Did you actually check the performance? The driver doesn't report tx > rate properly due to firmware limitation so it always reports 1mbps or > 6mbps to userspace tools. > > Sidenote: `iwconfig` is deprecated. `iw` is the go-to wireless tool now. > > > Michał > > _______________________________________________ > ath10k mailing list > [email protected] > http://lists.infradead.org/mailman/listinfo/ath10k >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
