From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 06:01:44 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE10716A4CE for ; Tue, 13 Jan 2004 06:01:44 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C6DD43D5E for ; Tue, 13 Jan 2004 06:01:40 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 99817307D1; Tue, 13 Jan 2004 09:01:39 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id D99271D1E34; Tue, 13 Jan 2004 07:28:51 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16387.58499.587197.601294@canoe.dclg.ca> Date: Tue, 13 Jan 2004 07:28:51 -0500 To: Sam Leffler In-Reply-To: <200401122149.06369.sam@errno.com> References: <16248.58260.560180.809655@canoe.dclg.ca> <200401122149.06369.sam@errno.com> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: freebsd-mobile@freebsd.org cc: David Gilbert Subject: Re: ATH driver doesn't associate with turbo. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 14:01:44 -0000 >>>>> "Sam" == Sam Leffler writes: Sam> On Monday 29 September 2003 06:59 pm, David Gilbert wrote: >> If I put my access point in turbo mode, the ath driver won't >> associate with it. Additionally, the documentation for my card >> says that it should support upto 108Mbps in turbo mode, but the ath >> driver doesn't detect this. Sam> What do you base this on? The turbo rates happen to be printed Sam> as 1/2 the actual speed.because the actual rate is done by Sam> overclocking and not by negotiating a different xmit rate. I've Sam> thought about artificially printing them as 2x values so people Sam> stop complaining. :) Fair enough. If this is the case, then things are correct. Sam> As to not being able to associate in turbo mode; you don't show Sam> how you configured the interface. Atheros-based AP's that Sam> support "SuperG" use a proprietary protocol handshake to Sam> negotiate use of turbo mode. The current driver doesn't support Sam> this though I recently got the info I need to add it. For "old Sam> turbo" mode you have to manually enable it with ifconfig before Sam> the 802.11 layer will assoociate with a turbo AP. I've Sam> considered changing this but adding turbo mode channels to the Sam> scan list would more often than not just lengthen the scanning Sam> process and rarely be used. The access point is an A-only unit made by Netgear. It advertises turbo modes only upto 72 megabit in it's documentation. Concerning your 'rarely used' comment, is it that access points based on Athros are rare or that turbo mode itself is not that useful? Maybe it would be sufficient to have a mode 11a-turbo in addition to mode 11a that is not part of the automatic scan. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================