Oops hit the wrong button in the previous email and I sent it to you
only instead of replying to the list. Sorry about that. It's forwarded
below.
As promised attached you can find the full dmesg output when running
the 4.10.0 kernel *with the commit reverted*. If you want the output
with another
"use your own bmi ids". :-)
(yeah, this is going to make open source firmware for these things
more painful than it should be. :( )
-adrian
On 7 March 2017 at 01:54, Sven Eckelmann wrote:
> Hi Adrian,
>
> On Montag, 30. Januar 2017 08:36:19 CET Adrian Chadd wrote:
>> If people aren't using u
> Could you share the logs with both driver and hostapd (-vvv), please?
# dmesg | grep ath
[3.263913] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[3.545202] ath10k_pci :02:00.0: Direct firmware load for
ath10k/pre-cal-pci-:02:00.0.bin failed with er
Thank you for looking into this.. I'm really sorry for the confusion, my second
email reversed what the problem really is. Now clarified **below**:
Is it possible to control spectral_scan_ctl whilst in **Monitor mode**?
my result:
root at OpenWrt:~# echo disable >
/sys/kernel/debug/ieee80211/ph
Hi Adrian,
On Montag, 30. Januar 2017 08:36:19 CET Adrian Chadd wrote:
> If people aren't using unique BMI IDs (which is another question we
> have for QCA) then it's possible you don't have enough information to
> "know" which board data to use, so it has to be overridden by a custom
> package. W
