Hi all,
I have played around a little bit with the raw mode patches trying to
get mesh working on ath10k. I've hacked the driver slightly to use an
AP vif in the firmware in mesh mode, which seems to produce proper looking
beacons over the air.
However, when I bring up a second mesh node, the
Michal Kazior michal.kaz...@tieto.com writes:
On 22 April 2015 at 08:27, Kalle Valo kv...@qca.qualcomm.com wrote:
Kalle Valo kv...@qca.qualcomm.com writes:
Michal Kazior michal.kaz...@tieto.com writes:
To reduce support questions from the users it would be nice to give few
good examples
Hi, Bob
I have tried converting the adhoc mode on the
firmware-2.bin_999.999.0.636 as mesh interface.
You can find my patches here:
https://github.com/chunyeow/ath/commits/mesh
But probably too many workaround and won't be able to interoperate
with other mesh interface.
I have also found out
Michal Kazior michal.kazior at tieto.com writes:
https://gist.github.com/kazikcz/c970cbf3a863ebbc4495
https://gist.github.com/kazikcz/64313b9e2470660faae1
Here are two simple and crude tools I have to deal with ath10k FW API
blobs. Use with care.
You can use the disassemble.py to
Hi Gabriele,
I have had success with eeprom_ar6320_2p1_NFA344i.bin.
I am also using Gentoo (but v3.19.3) but I have also applied these
patches/commits:
- http://permalink.gmane.org/gmane.linux.kernel.wireless.general/137030
-
On 04/24/2015 10:55 AM, Yeoh Chun-Yeow wrote:
Hi, Bob
I have tried converting the adhoc mode on the
firmware-2.bin_999.999.0.636 as mesh interface.
You can find my patches here:
https://github.com/chunyeow/ath/commits/mesh
But probably too many workaround and won't be able to interoperate
