Return-path: Received: from mail-vb0-f54.google.com ([209.85.212.54]:40625 "EHLO mail-vb0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752448Ab3KANpM (ORCPT ); Fri, 1 Nov 2013 09:45:12 -0400 Received: by mail-vb0-f54.google.com with SMTP id q12so2897946vbe.27 for ; Fri, 01 Nov 2013 06:45:11 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1383199449-18310-1-git-send-email-yeohchunyeow@gmail.com> Date: Fri, 1 Nov 2013 13:45:11 +0000 Message-ID: (sfid-20131101_144519_293398_E7E7E676) Subject: Re: [PATCH] wcn36xx: enable the beaconing in mesh mode From: Eugene Krasnikov To: Yeoh Chun-Yeow Cc: Thomas Pedersen , linux-wireless , John Linville , wcn36xx , Chun-Yeow Yeoh , "devel@lists.open80211s.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: I do not really remember what was the result of testing when we set tim_ie_offset to 0. Could you please share what do you observe when tim_ie_offset? Does FW corrupt beacon? My concern about 256 is that FW may corrupt some memory. Also assume the reason why FW sets TIM is because you configure FW as AP instead of mesh with this line: bss->bss_type = WCN36XX_HAL_INFRA_AP_MODE; On Fri, Nov 1, 2013 at 4:33 AM, Yeoh Chun-Yeow wrote: >> >> Also mesh beacon does need the TIM< only it must be generated by >> mac80211. How do you tell the firmware to ignore the beacon TIM? > > > Hi, Thomas > > The HAL send beacon request message requires the tim_ie_offset to be set. > There is another p2p_ie_offset in the request message. By setting it to 0, > it seems that the firmware ignores this IE while building the beacon. > However, I try to set the tim_ie_offset to 0. But this won't work. > > Hi, Eugene > > Did you ever test the tim_ie_offset set to 0? > > ---- > Chun-Yeow > -- Best regards, Eugene