From owner-freebsd-wireless@FreeBSD.ORG Mon Sep 5 23:45:24 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 9A86F106564A for ; Mon, 5 Sep 2011 23:45:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 582428FC19 for ; Mon, 5 Sep 2011 23:45:24 +0000 (UTC) Received: by vws18 with SMTP id 18so5512796vws.13 for ; Mon, 05 Sep 2011 16:45:23 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vfN/FH4DnjRkinPF/AnJbEj8qagyMcJ+Mi/Rfw66Ji4=; b=fiPSthNJbNf5kp3fUiZujQ/7vcsulYHlAZg9GC+pEHHR7hozXuGSTKG9m8iKjNlzT/ rijDX8JGCsy48bJRTp7cHgJRmSJE3l1I3IQ1hx2+iH3oFxLh8kLoDaYKb/bYneSnoXyL 12YwLV6cfnSF9h2jdhQH91Vx74KGD9VZ/IsQg= MIME-Version: 1.0 Received: by 10.52.20.106 with SMTP id m10mr4301412vde.328.1315266323719; Mon, 05 Sep 2011 16:45:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.33.49 with HTTP; Mon, 5 Sep 2011 16:45:23 -0700 (PDT) In-Reply-To: References: Date: Tue, 6 Sep 2011 07:45:23 +0800 X-Google-Sender-Auth: K_fRqojIgnXIZwRMwpPKA8-p2m8 Message-ID: From: Adrian Chadd To: Berislav Purgar Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 05 Sep 2011 23:45:24 -0000 .. since you're using the AR5416, I'll add in the missing bits. So the platform limitations I'm aware of are: * There's a TX bug somewhere which requires a chip reset when it occurs. I'll port that over today. * RTS protected aggregate frames are limited to 8k in size. Since I'm not (yet) doing RTS or CTS protected HT frames, this isn't a big deal for you. I'll see about trying to get the specific work around that improves performance when RTS is enabled. Since I'd like to investigate supporting MIMO power save (does anything _DO_ MIMO power save these days? I have no idea), and MIMO-PS requires functional 11n RTS frame protection, I'd like to make sure the RTS protected 11n aggregates are properly handled on the AR5416. Thanks, Adrian