From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 6 09:22:34 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 80F8B106566B; Tue, 6 Sep 2011 09:22:34 +0000 (UTC) (envelope-from bpurgar@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2855D8FC14; Tue, 6 Sep 2011 09:22:33 +0000 (UTC) Received: by gyd10 with SMTP id 10so4305309gyd.13 for ; Tue, 06 Sep 2011 02:22:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=73L6TLYZXFIDyRkxNxHVRqSBmTgZ08kyOcdBjfPQ758=; b=DIl3WsuksC5bBus4Qlv9R189uH1ZqN2QtSk8x/0QiJOU825UloKTwqw5qyg3oOQLl8 amGvmIMewLxQbkxaayA6R6cq5IeG7txMC0iy+NXGUKh0z/3a5zaKpu/bLs+WROaySYZA 58jFYWY4NOL3eXf4E55ivkAOS/sokZQsrX3sc= MIME-Version: 1.0 Received: by 10.68.14.100 with SMTP id o4mr5959255pbc.340.1315300952922; Tue, 06 Sep 2011 02:22:32 -0700 (PDT) Received: by 10.142.49.6 with HTTP; Tue, 6 Sep 2011 02:22:32 -0700 (PDT) In-Reply-To: References: Date: Tue, 6 Sep 2011 11:22:32 +0200 Message-ID: From: Berislav Purgar 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: ath 802.11n ampdutx progress ?? 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: Tue, 06 Sep 2011 09:22:34 -0000 On Tue, Sep 6, 2011 at 7:08 AM, Adrian Chadd wrote: > .. I think I've found/fixed the current BAW tracking bug. > There's more to go, but this should eliminate the obviously broken > case I introduced in an earlier commit. > Please try the latest code in my if_ath_tx branch and let me know. :) > > > Adrian > on my laptop where is 5416 works perfect. no more errors . on second PC where is 9280 and act as AP i still have same errors but not often like before on 5416. now i compile module for PC to test. Beri