Return-path: Received: from L01SLCSMTP01.calltower.com ([69.4.184.248]:16069 "EHLO L01SLCSMTP01.calltower.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752447AbZFCSKS (ORCPT ); Wed, 3 Jun 2009 14:10:18 -0400 Subject: Re: ar9170 vs otus advice? From: Jon Loeliger To: Christian Lamparter Cc: linux-wireless@vger.kernel.org In-Reply-To: <200906032032.25344.chunkeey@web.de> References: <1243894020.1559.22.camel@bigfoot-m4a75t> <200906030337.27448.chunkeey@web.de> <1244044799.1559.38.camel@bigfoot-m4a75t> <200906032032.25344.chunkeey@web.de> Content-Type: text/plain Date: Wed, 03 Jun 2009 13:09:58 -0500 Message-Id: <1244052598.1559.42.camel@bigfoot-m4a75t> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, 2009-06-03 at 20:32 +0200, Christian Lamparter wrote: > I'm not aware of any problems with/as a 802.11a/b/g station, > no one has reported any so far: so a/b/g works as _advertised_. > (at least for me and other developers) OK, good! > > Is the in-tree Otus up-to-date with all of these workarounds? > I'm not really sure. the latest (and last) otus driver can be found here: > http://www.kernel.org/pub/linux/kernel/people/mcgrof/otus/ > > That said, I could get a decent HT20 (up to 70Mbits tx & 90 Mbit rx) > performance with the in-kernel driver... Does it work for you as well, > or are you asking, because it doesn't? I'm just working on setting expectations (mine) so far, and getting a handle on what is presumed working so that I may choose the correct starting point for some work I would like to do. I've not tested it yet. > Regards, > Chr Thanks, jdl