From owner-freebsd-mobile@FreeBSD.ORG Tue Nov 8 23:36:41 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5643E1065677; Tue, 8 Nov 2011 23:36:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id C019B8FC13; Tue, 8 Nov 2011 23:36:40 +0000 (UTC) Received: by vcbfo14 with SMTP id fo14so1386138vcb.13 for ; Tue, 08 Nov 2011 15:36:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=RMsMliM6DY5IOy62EWI0L4EpCrSNnnzqgP/5zFEODzA=; b=DSt3+5BP4a48/lC4+qL8o5qmWhT/otdSVp3YwILpeglpKW45t1BmVTtrh+eaLIiyMq pr3vfw4OuaHLUiyG8lKc2GzOr8i7H4TMlVUJkd3ZdfwV7iKPpRCFUrxYsf7T1z+hlhqz TToMSSJ8bBRhPHIVY2fMBid5PuIQKkMSIb9iM= MIME-Version: 1.0 Received: by 10.52.177.3 with SMTP id cm3mr34659472vdc.89.1320795399970; Tue, 08 Nov 2011 15:36:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.29.198 with HTTP; Tue, 8 Nov 2011 15:36:39 -0800 (PST) Date: Tue, 8 Nov 2011 15:36:39 -0800 X-Google-Sender-Auth: Y2O0f1ETVyi8jh9GZrRWPjktwLQ Message-ID: From: Adrian Chadd To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Net , freebsd-wireless@freebsd.org, freebsd-mobile@freebsd.org Subject: ath 11n tx work is now in head X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2011 23:36:41 -0000 Hi, I've merged in the bulk of my 11n TX work in a series of commits, culminating in a (still) overly large patch which added software TX aggregation and TX queue support. It's absolutely possible this has completely broken the ath driver. I'm going to spend the next few days throwing it against the hardware I have with me just to see if I broke anything during the merge. If you feel brave, throw on ATH_ENABLE_11N in your kernel config file and give it a go. If you're using legacy (non-11n) NICs, or you're not using 11N at home, please enable it too. It affects the non-11n TX path as well and I'd like to make absolutely sure this is still (mostly) working. Finally, if you -are- going to be testing this, I won't accept any error reports unless you've been running it with the -current debugging flags. That is, lock/witness debugging, asserts, and the memory allocator debugging. There's just too much that could be going wrong and I'd like to make sure that I have all of the relevant information from testers. Thanks again! Adrian