From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Vtx9R-00065l-PF for ath10k@lists.infradead.org; Fri, 20 Dec 2013 10:17:50 +0000 From: Kalle Valo Subject: Re: Unable to receive beacon in IBSS mode References: Date: Fri, 20 Dec 2013 12:17:07 +0200 In-Reply-To: (Yeoh Chun-Yeow's message of "Thu, 19 Dec 2013 21:28:47 +0800") Message-ID: <87a9fv3jz0.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 Yeoh Chun-Yeow writes: > I have observed if you create the interface in the ath10k as IBSS mode > (WMI_VDEV_TYPE_IBSS). The ath10k_wmi_event_mgmt_rx is not able to > receive the beacon frame. This maybe the reason when the STA up as > adhoc mode not able to join the network. > > But if you put the ath10k as AP mode (WMI_VDEV_TYPE_AP), you are able > to receive the beacon. > > Is this the correct behavior? I haven't done any IBSS tests myself, but what firmware version are you using? -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k