From owner-freebsd-wireless@FreeBSD.ORG Tue Jun 19 00:51:42 2012 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 A62D71065673; Tue, 19 Jun 2012 00:51:42 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2CEA28FC08; Tue, 19 Jun 2012 00:51:42 +0000 (UTC) Received: by qcsg15 with SMTP id g15so3910404qcs.13 for ; Mon, 18 Jun 2012 17:51:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=/bNFVtQQu1IdVRPE5sPSzFVolIh6T4OI5JQi0YXtmPs=; b=TRO273FivTBBHPNZ1i5JClkokRLAVJQPIFN094LnmoyTxH4WNLkLapnofI1Boni40y rP+vSUvSbSv6hrpahxEGgtc1e9Tu9C0+e+En+mZr/nmolumu0uIPLXfAdkA2kPXYOjAs HRQvbJDowMyyF5GIy3PB+sbUBa+PcEnBymoTlxBSaL3h9YNcLwku6EibXXkrJKBNqyHg flEeQyFdmBKpvg6scFEi8LfEhEef7r/rX7OgRa7+pEymCxUtu5dYtkFQfWqOGLJSoS/t ibgcS5e+T/TkYyi6fZIpV6jbuqf7NrMUeeL9FSKK/2uuwFjEUBLyN6/5wXpnlaLUmD6j XBtA== Received: by 10.224.72.138 with SMTP id m10mr30896674qaj.5.1340067101591; Mon, 18 Jun 2012 17:51:41 -0700 (PDT) Received: from narn.knownspace (pool-72-83-55-7.washdc.fios.verizon.net. [72.83.55.7]) by mx.google.com with ESMTPS id ei10sm44859394qab.20.2012.06.18.17.51.40 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Jun 2012 17:51:41 -0700 (PDT) Date: Mon, 18 Jun 2012 20:51:37 -0400 From: Justin Hibbits To: Adrian Chadd Message-ID: <20120618205137.344191a0@narn.knownspace> In-Reply-To: References: X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; powerpc-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: ath(4) now defaults to 802.11n on GENERIC/i386 and GENERIC/amd64 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, 19 Jun 2012 00:51:42 -0000 Hi, On Fri, 15 Jun 2012 01:17:31 -0700 Adrian Chadd wrote: > Hi, > > I've flipped on ATH_ENABLE_11N and the interrupt mitigation in i386 > and amd64 GENERIC. > > I'll flip it on on PPC when someone (chmee?) verifies that 802.11n > works on PPC. I did my duty as PPC guinea pig, and can happily say that unlike other cards *cough*bw{i,n},wi*cough* I can actually use ath on my PowerBook. AR5416, about as stable as I've seen so far. I think you can flip it on PPC now. > > It's still delicate. I still don't know if RTS/CTS HT frame protection > is working quite right on all chips. But all the basics are there > (software TX aggregation, RX AMPDU reordering in net80211, BAR > transmission, software queue pause and unpause, frame retransmission.) > > Don't be surprised if your 802.11n mobile devices perform poorly as > the power queue handling is very broken and will result in all kinds > of weird traffic stalls if things are too aggressive. I'll look into > fixing that soon. > > If you have problems, please read the wiki article: > http://wiki.freebsd.org/dev/ath(4) - specifically the bits where I > tell you to compile with the debugging and diagnostic stuff in your > -HEAD kernel, including the HAL/driver diagnostic APIs and tools. > > Enjoy, > > > > Adrian If I can reproduce that crash I mentioned on IRC, I'll post what I can about it. - Justin