From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from sabertooth01.qualcomm.com ([65.197.215.72]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1W85vC-0000yP-CY for ath10k@lists.infradead.org; Tue, 28 Jan 2014 10:29:34 +0000 From: Kalle Valo Subject: Re: Unable to receive beacon in IBSS mode References: <87a9fv3jz0.fsf@kamboji.qca.qualcomm.com> <87wqiz24my.fsf@kamboji.qca.qualcomm.com> Date: Tue, 28 Jan 2014 12:28:59 +0200 In-Reply-To: (Yeoh Chun-Yeow's message of "Mon, 23 Dec 2013 15:47:20 +0800") Message-ID: <8761p4iems.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: Yeoh Chun-Yeow Cc: ath10k@lists.infradead.org Hi, Yeoh Chun-Yeow writes: > It seems that the problem of adhoc mode is due to the get_tsf is not > implemented in the driver. > > Can you point out which WMI command that we can use to fetch the TSF timestamp. I took a quick look at firmware and I didn't find a way to do that. But I'm no firmware engineer so I might have just missed it. Can you describe in more detail how adhoc is failing? -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k