From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 24 10:31:09 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46BF9106564A; Wed, 24 Aug 2011 10:31:09 +0000 (UTC) (envelope-from paradyse@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id DE4988FC0C; Wed, 24 Aug 2011 10:31:08 +0000 (UTC) Received: by ywo32 with SMTP id 32so858721ywo.13 for ; Wed, 24 Aug 2011 03:31:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=ZGK6QlMKSt2NKv5fCAVjf7JKtC6OJcOCm3cOu24J0ZI=; b=oRBjhzJnEew59zS3LTIqiPP786XrUPXpDpCKxVriSZue/SItKfia7fMa1vpyx4wh2/ HbbGl3tJEaCbUhuNzOOM46FoN6tg/REVyg03SaHiADtkGkCNPnKXrdC0sUm3rQ/a6zu8 bGTjeipc6qYds1SmJRMs1gkfHZtGN20E5BUeE= Received: by 10.150.198.18 with SMTP id v18mr5066626ybf.24.1314181868164; Wed, 24 Aug 2011 03:31:08 -0700 (PDT) MIME-Version: 1.0 Sender: paradyse@gmail.com Received: by 10.151.43.7 with HTTP; Wed, 24 Aug 2011 03:30:48 -0700 (PDT) In-Reply-To: References: From: Kang Yin Su Date: Wed, 24 Aug 2011 18:30:48 +0800 X-Google-Sender-Auth: fA56ceFOwBbgc6sS2WLvtzm-1IQ Message-ID: To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: AR5416 beacon issue. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Aug 2011 10:31:09 -0000 There is no SWBA interrupt to trigger beacon send, looks like something invalid in beacon timer. -Yin On Wed, Aug 24, 2011 at 5:51 PM, Adrian Chadd wrote: > On 24 August 2011 17:40, Kang Yin Su wrote: > > Still no beacon frames TX' from TDMA mode. Do you have idea what is this? > > It sounds like maybe the beacon gating of the TX queue is not functioning? > It's possible that MAC changes between AR5212 and AR5416 are the problem? > > > "ar5416PerCalibrationN: NF calibration didn't finish; delaying CCA" > showing > > while the TDMA wlan0 interface is brought up > > Oh, that can be ignored. It just meant the initial NF calibration > during interface setup didn't complete very quickly, so it's delaying > the CCA load (as the values needed aren't yet available.) > The initial NF calibration can sometimes take quite a bit longer than 10ms. > > Adrian >