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

[Kalle Valo]

Sven Eckelmann <sven at open-mesh.com> writes:

> On Saturday 18 January 2014 01:14:28 Kalle Valo wrote:
>
>> > 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.

The bug report doesn't need to be perfect, not all bugs are easily
reproducable, but just knowing about a bug would even help. That's why
ask people to send bug reports to ath10k at lists.infradead.org.

>> >  * 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?

So we have two firmware branches right now, "main" and "10.1". 10.1 is
solely focused on AP mode, nothing else. The main branch again has more
features, like P2P, but doesn't support AP mode as well as 10.1 does.

-- 
Kalle Valo