From owner-freebsd-wireless@FreeBSD.ORG Fri Mar 9 09:40:10 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 71A0E106566B for ; Fri, 9 Mar 2012 09:40:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id E65D28FC17 for ; Fri, 9 Mar 2012 09:40:09 +0000 (UTC) Received: by lagv3 with SMTP id v3so1955054lag.13 for ; Fri, 09 Mar 2012 01:40:08 -0800 (PST) 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:content-type; bh=7ed7shQBAhOH8f9wNUecvPJt9lfw0bi8D68YMcd3/1s=; b=G87OUQ8mfzxNopXYtbmOTA14dyWzuUatMbGp+ul/aqhcnschvwG45y2yF4ZecHJzrG fUsNbREOBUc0cJ9qaAI9cz2QNHD5SHpK8WqdTbOtwbhXBRxrNTd68Ms9zuvBmxPuMXdl ZzpqzpBmVlR8NZXwvHzEkTgYgsPQPltdK78+3UJrbNQ2d+gvUWfJfrKNrRB+mDekqNXD B4rMXz+akOkRcFaorl/nnOta8czLhC4HXRwLewVWtx2vbNVMewzXlRvLqS7iqszis/ih yl35KXz2glOi9pXnoS8tYiMqONsnbi4JKxDF3hlmfze1qNEiJ1QnmVbAM+G2SMjjZbRi EqoA== MIME-Version: 1.0 Received: by 10.152.148.230 with SMTP id tv6mr1119777lab.12.1331286008645; Fri, 09 Mar 2012 01:40:08 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.112.13.18 with HTTP; Fri, 9 Mar 2012 01:40:08 -0800 (PST) Date: Fri, 9 Mar 2012 01:40:08 -0800 X-Google-Sender-Auth: EL7EDPEFgCuaIblZ10cTS5bLYyg Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: (more) bugs fixed in -HEAD, AP mode is now mostly (again) stable! 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: Fri, 09 Mar 2012 09:40:10 -0000 Hi all, I just fixed a rather silly/ridiculous bug that I introduced into ath(4) when I reworked the reset path to not just purge frames during an interface reset. The 11na/11ng stuff is now stable again. I didn't notice it before because I didn't have enough background traffic _and_ interface rests. Silly me. :( In any case, if you've been waiting to upgrade to a -HEAD checkout to do more 11n testing, now would be a good time. Just remember to disable background scan or things will definitely hang on you. Next - BAR handling and correct queue pause/resume handling. Then I can flip it on by default! Adrian