Return-path: Received: from mail-vc0-f180.google.com ([209.85.220.180]:61678 "EHLO mail-vc0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752493AbaDXIuQ (ORCPT ); Thu, 24 Apr 2014 04:50:16 -0400 Received: by mail-vc0-f180.google.com with SMTP id hq16so85727vcb.11 for ; Thu, 24 Apr 2014 01:50:15 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1398327250-12923-1-git-send-email-yeohchunyeow@gmail.com> Date: Thu, 24 Apr 2014 16:50:15 +0800 Message-ID: (sfid-20140424_105022_647673_4648B190) Subject: Re: [PATCH] ath10k: don't allow stand alone monitor mode for non-AP firmware From: Yeoh Chun-Yeow To: Michal Kazior Cc: linux-wireless , "ath10k@lists.infradead.org" , Kalle Valo Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: > 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? ---- Chun-Yeow