[PATCH] ath10k: don't allow stand alone monitor mode for non-AP firmware

Yeoh Chun-Yeow yeohchunyeow at gmail.com
Thu Apr 24 02:09:25 PDT 2014

On Thu, Apr 24, 2014 at 4:53 PM, Michal Kazior <michal.kazior at tieto.com> wrote:
> On 24 April 2014 10:50, Yeoh Chun-Yeow <yeohchunyeow at gmail.com> wrote:
>>> I think Monitor operation should be performed on a best effort basis.
>>> This means monitor_start/stop should be attempted once number of
>>> non-monitor vdevs changes.
>> I am too clear about this. Do you mean that actually we can have
>> monitor mode on non-monitor vdevs in firmware 636?
> No. What I mean is we should attempt to start monitor vdev once at
> least 1 non-monitor vdev is present and stop monitor vdev is last
> non-monitor vdev is about to be stopped on 636.

Got it. But my investigation on firmware 636 shows that the firmware
crashes even though 1 non-monitor vdev is present. So can we conclude
actually monitor mode is not allowed in firmware 636.


More information about the ath10k mailing list