From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail2.candelatech.com ([208.74.158.173]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1WzmUp-0006tV-NS for ath10k@lists.infradead.org; Wed, 25 Jun 2014 12:40:16 +0000 Message-ID: <53AAC317.4050403@candelatech.com> Date: Wed, 25 Jun 2014 05:39:51 -0700 From: Ben Greear MIME-Version: 1.0 Subject: Re: CT and AP firmware not allowed beaconing in adhoc mode References: In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Michal Kazior , Yeoh Chun-Yeow Cc: "ath10k@lists.infradead.org" On 06/25/2014 05:33 AM, Michal Kazior wrote: > On 25 June 2014 06:50, Yeoh Chun-Yeow wrote: >> Hi, all >> >> Both CT and AP firmware seem not allow beaconing in adhoc mode. >> Anyone will fix this? > > AP firmware doesn't really support IBSS. I guess ath10k shouldn't > advertise the iftype if 10.1 firmware is used. > > As far as I know CT firmware is based on the AP firmware branch which > means no IBSS as well. That is true. I have not had any time to see what it would take to support IBSS in the 10.1.x firmware, and do not have access to the 999.x source to see what it does differently. I'm not sure when I'll have time to work on it.... Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k