ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Michael Krupp <michaelkrupp@gmx.net>
To: michal.kazior@tieto.com
Cc: ath10k@lists.infradead.org
Subject: Re: Support for QCA6174 [168c:003e]
Date: Tue, 27 Oct 2015 12:22:05 +0100	[thread overview]
Message-ID: <562F5E5D.5090205@gmx.net> (raw)
In-Reply-To: <CA+BoTQm59x1KZGrkqXZAMfqoe5=Z03wszvWiNw+feqNinsa9Hw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1798 bytes --]

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 <michaelkrupp@gmx.net> 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
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
> 


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2015-10-27 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-25  3:57 Support for QCA6174 [168c:003e] Michael Krupp
2015-10-26  7:20 ` Michal Kazior
2015-10-26 21:18   ` Michael Krupp
2015-10-27  6:22     ` Michal Kazior
2015-10-27 11:22       ` Michael Krupp [this message]
2015-10-27 11:27         ` Michal Kazior
2015-10-27 12:01           ` Michael Krupp
2015-10-29 20:44             ` Michael Krupp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=562F5E5D.5090205@gmx.net \
    --to=michaelkrupp@gmx.net \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).