From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1XRjnw-0001FO-29 for ath10k@lists.infradead.org; Wed, 10 Sep 2014 15:27:32 +0000 From: Kalle Valo Subject: Re: Firmware crash w/ 10.2 diagnosis? References: <87tx4h8096.fsf@kamboji.qca.qualcomm.com> Date: Wed, 10 Sep 2014 18:26:52 +0300 In-Reply-To: (Denton Gentry's message of "Tue, 9 Sep 2014 13:05:21 -0700") Message-ID: <8761gv7ayr.fsf@kamboji.qca.qualcomm.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Denton Gentry Cc: Michal Kazior , "ath10k@lists.infradead.org" Denton Gentry writes: > I'm using backports, and the kernel version is 3.2. > hostapd says it is indeed using the cooked monitor: > > monitor mode needed: 1 (poll_cmd=1 data_tx_status=0) > > I'll look at updating the kernel, if not to 3.16 then at least to > something recent enough to stop using the monitor interface from > hostapd. Good. But if you use bridging the monitor vdev is created anyway. So most likely switching to nl80211 management frame interface is not going to workaround the firmware bug. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k