From owner-freebsd-wireless@FreeBSD.ORG  Fri Jun 15 08:17:32 2012
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4E3F91065672;
	Fri, 15 Jun 2012 08:17:32 +0000 (UTC)
	(envelope-from adrian.chadd@gmail.com)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com
	[209.85.210.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 1D7128FC08;
	Fri, 15 Jun 2012 08:17:32 +0000 (UTC)
Received: by dadv36 with SMTP id v36so3901700dad.13
	for <multiple recipients>; Fri, 15 Jun 2012 01:17:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:x-google-sender-auth:message-id:subject
	:from:to:cc:content-type;
	bh=ftke2i5RgOVC+oOOVf5kU47E0mTGDKPSBjINb26GODc=;
	b=E7jXSi86scQoLqetrTwzxBBI98dHU8b8lhfkDuORcW9JmXSnHtFbTv6uJcVuDSX2YP
	OQl2Q03injlKcdFhOtlhW2BUAIh9B1Rra5xoo1qBVp9DjsVIPS1tLuf/t8+Z/21AK9J1
	W4xCDMHfQa1Qa+SNBlbJPWt6PhzDLW5Q4jQlhBbdnuLI1yKPxXlhEb+t3IMZougCEg/B
	5dsLDNLtldZ3Fu9klOScFE+LLRns7eLx29mQWoMxDPKEb9B9H/VzR4QocMWGTp6S++a0
	zJ6JLqKSqM+uclOiVsET5AAyn0SakVfL7h9YRZWEpUS/tFWmvWlrQ+P8TySsQBA+D1Wy
	yRjg==
MIME-Version: 1.0
Received: by 10.68.116.203 with SMTP id jy11mr17260290pbb.129.1339748251877;
	Fri, 15 Jun 2012 01:17:31 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.143.91.18 with HTTP; Fri, 15 Jun 2012 01:17:31 -0700 (PDT)
Date: Fri, 15 Jun 2012 01:17:31 -0700
X-Google-Sender-Auth: Af5YpSJhLW7_vwqoWKL28otKc7E
Message-ID: <CAJ-Vmok=9RosrDPHveJWA_+2Av=+OnstHU7W=QmNpmUHiANR9w@mail.gmail.com>
From: Adrian Chadd <adrian@freebsd.org>
To: freebsd-current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-wireless@freebsd.org
Subject: 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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 08:17:32 -0000

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.

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