gistfile1.txt

08:41 < DonkeyHotei> greearb: any chance -ct fw can ever be made to work on 9880-ar1a chips?
08:42 < ultito> how about my reported issue about named process?
08:42 < DonkeyHotei> ultito: should be easy to patch and submit a PR
08:42 < greearb> the driver removed the awful hacks needed to sort of make the v1 hardware work long ago, I doubt it will ever be added, and not sure it can really be fixed, so probably that is never supported.
08:43 < greearb> assuming -ar1a means -v1 hardware
08:43 < ultito> DonkeyHotei: Great!!!
08:43 < DonkeyHotei> ultito: change START=50 to START=97
08:43 < Monkeh> greearb: It does
08:43 < Monkeh> greearb: I'm guessing those chips are fundamentally broken or just plain stupid
08:43 < greearb> that is my understanding
08:44 < ultito> DonkeyHotei: yes, I did it :-) But it should be pre-set in new release for all to prevent problem I found
08:44 < Monkeh> greearb: But they made sure to beta test them with paying customers. :)
08:46 < DonkeyHotei> i know "fixed" it too pie-in-the-sky, but people keep running into c7v1's and the current driver causes a bootloop on those
08:46 < greearb> yeah, I bought a bunch of those when they first came out, but they were useless.
08:47 < DonkeyHotei> s/it/is/
08:48 < Monkeh> Well perhaps just fix the cause of the presumably kernel panic.
08:48 < DonkeyHotei> "sort of working" would be great though
08:49 < Monkeh> Not remotely worth the bother
08:49 < DonkeyHotei> best ath10k in general can do anyway is "sort of working"
08:50 < Monkeh> Bitching and moaning vaguely about issues does not help fix them
08:51 < DonkeyHotei> qualcomm does not exactly offer many alternatives
08:54 < greearb> for v1, I'd suggest hacking the ath10k/pci.c to cause it to not even try to load that chipset.  Maybe that AP has a 2.4 radio that can work at least?