[PATCH 0/2] Initial 11ac support using ath10k

[Sven Eckelmann]

On Saturday 18 January 2014 01:14:28 Kalle Valo wrote:
> > I've picked up the patches and rebased them on top of the current master
> > branch/trunk.
> 
> Where did you take the ath10k patches? ath10k is under heavy
> development, so I strongly recommend taking patches directly from
> ath-next branch of my ath.git. That way you would be using the latest
> and greatest.

They were taken from the wireless-testing repo. But it seems that (for obvious 
reasons) the OpenWrt maintainers doesn't want so apply so many patches. But it 
is a good source [1] for future tests.

> > Just as general information to the state of ath10k, my current test showed
> > 
> > some problems with it:
> >  * Samsung GT-I9300 only got horrible slow connections to an QCA9880 but
> >  
> >    an Intel N6205 (using iwlwifi from v3.12) or Samsung S4 worked
> >    "fine"
> 
> Could you report the I9300 issue to the ath10k list with more details,
> please? We can try to investigate it.

This is a little bit problematic. I could reproduce this problem quite well on 
a specific date and when I tried some other day it worked fine. So it is hard 
to report anything. The only thing I could report would be the "Failed to add 
peer" problem which seemed to happen at the same time.

Maybe I find a way to reproduce it reliable but I don't know how at the 
moment.

> >  * Adhoc mode doesn't work at all
> 
> That was with 10.1 firmware? AFAIK it doesn't support adhoc at all. I
> think we need to add a firmware feature flag to disable adhoc with that
> firmware.

It used the latest and greatest, stable(?) version of the firmware when the 
patchset was generated: ap/firmware-2.bin_10.1.467-1

The statement "doesn't support adhoc at all" makes me a little bit nervous. 
Would you say that it is better to completely ignore the "ap" directory of the 
firmware repo [2]? Which benefits does the ap firmware has over the ath10k 
firmware?

At the end I would most likely run something like this:

 * 1 AP dev with WPA (1/2, TKIP and/or CCMP, PSK or Enterprise)
 * 1 AP dev without WPA
 * 1 adhoc dev with IBSS RSN (running something like batman-adv over
   infrastructure mode is a little bit lame ;) )

But it also has to be able to use a dev in managed mode.

This worked quite well in the past with ath9k and thus I was checking ath10k 
to decide if it is an interesting platform/driver for the future.

> >  * Sometimes adding of station seems to fail:
> >    ath10k: Failed to add peer 5c:0a:5b:4e:6a:c4 for vdev 1 when adding a
> >    new
> >    sta: -145
> 
> This is new to me. Can you report this to the ath10k list, please?

I will try to reproduce it and report it in a separate thread when I have more 
useful information.

> >  * Adhoc interface +  "iw dev wlan0 scan trigger" just crashes the 
firmware:
> >    [ 296.160000] ath10k: firmware crashed!
> >    [ 296.170000] ath10k: hardware name qca988x hw2.0 version 0x4100016c
> >    [ 296.170000] ath10k: firmware version: 65.467.0.0
> 
> What firmware version was this? The version printed here seems to be
> corrupted.

ap/firmware-2.bin_10.1.467-1

Kind regards,
	Sven

[1] https://github.com/kvalo/ath
[2] https://github.com/kvalo/ath10k-firmware
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20140120/48d6756d/attachment.sig>