From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ig0-f171.google.com ([209.85.213.171]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Yn4pa-0005K9-8e for ath10k@lists.infradead.org; Tue, 28 Apr 2015 12:41:43 +0000 Received: by igbyr2 with SMTP id yr2so89216220igb.0 for ; Tue, 28 Apr 2015 05:41:20 -0700 (PDT) Date: Tue, 28 Apr 2015 08:41:16 -0400 From: Bob Copeland Subject: Re: attempting mesh on ath10k Message-ID: <20150428124116.GC4527@localhost> References: <20150424125055.GA27722@localhost> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: 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: Ben Greear , "ath10k@lists.infradead.org" On Sat, Apr 25, 2015 at 01:55:32AM +0800, Chun-Yeow Yeoh wrote: > Hi, Bob > > I have tried converting the "adhoc" mode on the > firmware-2.bin_999.999.0.636 as mesh interface. > > You can find my patches here: > https://github.com/chunyeow/ath/commits/mesh > > But probably too many workaround and won't be able to interoperate > with other mesh interface. Yeah, I think adhoc will not work so well due to TSF sync and the distributed beacon algorithm. So I'm happy that AP approach seems viable; of course dedicated mesh vdev type would be nice :) -- Bob Copeland %% http://bobcopeland.com/ _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k