From owner-freebsd-current@FreeBSD.ORG Wed Sep 22 06:09:58 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D8811065670; Wed, 22 Sep 2010 06:09:58 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 14AC58FC16; Wed, 22 Sep 2010 06:09:57 +0000 (UTC) Received: by fxm9 with SMTP id 9so130942fxm.13 for ; Tue, 21 Sep 2010 23:09:57 -0700 (PDT) Received: by 10.223.120.76 with SMTP id c12mr7276026far.61.1285135796820; Tue, 21 Sep 2010 23:09:56 -0700 (PDT) Received: from jessie.localnet (p5B0E127F.dip0.t-ipconnect.de [91.14.18.127]) by mx.google.com with ESMTPS id r4sm4045985faa.43.2010.09.21.23.09.54 (version=SSLv3 cipher=RC4-MD5); Tue, 21 Sep 2010 23:09:55 -0700 (PDT) From: Bernhard Schmidt To: freebsd-current@freebsd.org Date: Wed, 22 Sep 2010 08:09:36 +0200 User-Agent: KMail/1.13.2 (Linux/2.6.32-24-generic; KDE/4.4.2; i686; ; ) References: <20100919120012.A77371065674@hub.freebsd.org> <367708.1588.qm@web51805.mail.re2.yahoo.com> In-Reply-To: <367708.1588.qm@web51805.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201009220809.36641.bschmidt@techwires.net> Cc: Adrian Chadd , PseudoCylon Subject: Re: RFT: if_ath HAL refactoring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 06:09:58 -0000 On Wednesday, September 22, 2010 06:04:49 PseudoCylon wrote: > ----- Original Message ---- > > > From: Adrian Chadd > > To: PseudoCylon > > Cc: freebsd-current@freebsd.org > > Sent: Tue, September 21, 2010 7:04:37 AM > > Subject: Re: RFT: if_ath HAL refactoring > > > > On 21 September 2010 11:58, PseudoCylon wrote: > > > Just in case anyone wonders, I've added 11n support to run(4) (USB > > > NIC). http://gitorious.org/run/run/trees/11n_beta2 > > > > > > It still has some issues, > > > > > > * doesn't work well with atheros chips > > > > > > * HT + AP + bridge = Tx may stall (seems OK with nat) > > > > > > So, use it at your own discretion. > > > > Want to put together a patch? > > sure! > > > Does it introduce issues in the non-11n case? > > No, only in 11n mode. > > What I have found so far is that Ralink's driver checks MAC address of > other end and identify atheros chip by oui. Then, sets special prot mode > for it. Does this ring a bell? Are your sure that this is based on the actual MAC addresses? Atheros drivers tend to announce additional capabilities in beacons and probe responses. > Has node lock in ieee80211_node_timeout() cased dead lock in HT + AP + > bridge? I'm not aware of any issues there, though, I'm not very familiar with HT use cases. -- Bernhard