Return-path: Received: from mail-oi0-f49.google.com ([209.85.218.49]:34682 "EHLO mail-oi0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753656AbbH3Rn3 (ORCPT ); Sun, 30 Aug 2015 13:43:29 -0400 Received: by oiex83 with SMTP id x83so53733577oie.1 for ; Sun, 30 Aug 2015 10:43:28 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20150829222531.GA8604@localhost> References: <1440673024-13696-1-git-send-email-me@bobcopeland.com> <1440673024-13696-4-git-send-email-me@bobcopeland.com> <20150829222531.GA8604@localhost> Date: Mon, 31 Aug 2015 01:43:28 +0800 Message-ID: (sfid-20150830_194333_659814_BD49353B) Subject: Re: [PATCH 3/3] ath10k: implement mesh support From: Yeoh Chun-Yeow To: Bob Copeland Cc: Jason Andryuk , "linux-wireless@vger.kernel.org" , "ath10k@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi, Bob > Yes: you don't want to enable raw mode TX / RX decap in the normal > case because it's fairly inefficient compared to "native" wifi mode, > according to my understanding. The latter doesn't support mesh framing > however. > The native WiFi mode doesn't support mesh framing. Can you elaborate more on this? Thanks ---- Chun-Yeow