> I just wanted to try out meshpoint interfaces with firmware 0x30804a5. 
> The
> change seemed to be a straight forward port from ath10k. But it turned 
> out
> that the firmware seems to behave significantly different. I saw three
> unexpected things:
> 
> 0. firmware dies immediately when using subtype 6 (MESH_11S) during 
> vdev
>    create
> 
>     [   28.663988] Fatal error received from wcss software!:
>     [   28.663988] QC Image Version: 
> QC_IMAGE_VERSION_STRING=WLAN.HK.1.1-01967-QCAHKSWPL_SILICONZ-1
>     [   28.663988] Image Variant : 
> IMAGE_VARIANT_STRING=8074.wlanfw.evalQ
>     [   28.663988]
>     [   28.663988] ar_wal_peer.c:7223 Assertion 
> !WAL_IS_TID_QOS_DATA(tidno) failedparam0 :zero, param1 :zero, param2 
> :zero.
> 
Sven,

Cool... The target assert was fixed in firmware. QCA also is bringing up
ath11k in MP and with attached list of changes, we were able to send 
traffic
open-mesh. Changes are not yet pushed to tree.

Below issues were observed in bring up and fixed in 
WLAN.HK.2.1.0.1-00113-QCAHKSWPL_SILICONZ-1 firmware

1) Assert in mesh interface creation.
2) Group action were filtered
3) fix 4 addr in firmware for mesh peers


Moving forward please use 2.1.0-1 firmware release which is meant for 
ath11k.
We are still working on to enable secured mesh (SAE).

-Rajkumar