From owner-freebsd-wireless@FreeBSD.ORG Thu Mar 21 03:53:18 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 31CE1EC2 for ; Thu, 21 Mar 2013 03:53:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id CB9396CC for ; Thu, 21 Mar 2013 03:53:17 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hm11so6662315wib.1 for ; Wed, 20 Mar 2013 20:53:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=WiDPDvxFAbU4UsCckSJ8W2IpCxNWgxfN7Mtu722YaNU=; b=tYIuGOM9bQiDKqaxmOtWcieC4HnZJFNE4xCeNWM3PhfCGiGRYp/07LCzb2aN8XPVcH +QPY7gE4BLSh8pUBbxBCjHFWPUKOEUoAytx9WQsdEDCxdjwD4z8KfC+y1FFNssMMRHaY FkF83YcTSMMK6pGpVqE41q0lvecC3uwh8IwbitwIFywc//T9fC4fSZ2vz5oKe+ake0uz etZQDYcc+hUN9nKkbJiBXcP53Tu3alv799QQcJ9TOSNZzR6tI9O9w+x7buGPB6TQQ0+/ 27/DBu2lwxr4VWzyK23kblmvjGR+afsS7IYqhlu0ma2gon26lmGZLcmlMQcsf3C7lchK jjhQ== MIME-Version: 1.0 X-Received: by 10.180.74.131 with SMTP id t3mr1956408wiv.26.1363837997044; Wed, 20 Mar 2013 20:53:17 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Wed, 20 Mar 2013 20:53:16 -0700 (PDT) Date: Wed, 20 Mar 2013 20:53:16 -0700 X-Google-Sender-Auth: RO7okTaZdkv0OKZkw_g6jJDP4_0 Message-ID: Subject: FYI: why hostap mode isn't ready yet for AR9380 and later chips From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 21 Mar 2013 03:53:18 -0000 Hi, I've had a few people ask why AR9380 hostap mode isn't working yet and when I expect to have that working. Firstly - it's because I have a day job, and that day job isn't FreeBSD. Honest. But all jokes aside, the last main thing to deal with at the moment is tidying up the TX path - specifically how the CABQ traffic is assembled. Right now any traffic that gets shoved in the CABQ confuses my TX FIFO hack to bring up unicast / station mode traffic, and this will eventually hang the driver. I'm designing some replacement TX code which will "fix" all of this but it's going to take time. So, as usual, it'll happen but it'll take time. It's not all bad news - I know that basic hostap services work, right up to 3x3 MCS23. So the basics are there and working fine. It's just the CABQ handling that is finally forcing me to do a redesign of that part of the codebase. I'll let everyone know when I have pushed some code into -HEAD for further testing. Thanks, Adrian