From mboxrd@z Thu Jan  1 00:00:00 1970
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Date: Tue, 3 Nov 2009 09:50:24 -0800
Subject: [ath9k-devel] 802.11n support in ad-hoc mode?
In-Reply-To: <058b01ca5cad$2226dbb0$66749310$@kaist.ac.kr>
References: <053501ca5c5d$38190c40$a84b24c0$@kaist.ac.kr>
	<057701ca5c9d$852907c0$8f7b1740$@kaist.ac.kr>
	<d355d36c0911030814l1342fd0cqd787cd34652c6b11@mail.gmail.com>
	<20091103162453.GB8503@tux>
	<058a01ca5ca5$1022b630$30682290$@kaist.ac.kr>
	<20091103173017.GD8503@tux>
	<058b01ca5cad$2226dbb0$66749310$@kaist.ac.kr>
Message-ID: <20091103175024.GF8503@tux>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On Tue, Nov 03, 2009 at 09:43:20AM -0800, Jinsung Lee wrote:
> At this time, I'm setting the rate using "iwconfig" command.
> It seems like it's working anyway.
> Of course, at most 54Mbps.

iwconfig will let you set the rate for legacy rates, that is -- not MCS rates.

> But, isn't it a good way to configure something like mode and rate via
> "iwconfig" command instead of "iw"?

iwconfig is a legacy utility. If I were you I'd uninstall it and
try to learn to use iw properly. Nothing new will be added through
iwconfig any more. Using iwconfig is fine but do not expect to gain
new features. iwconfig knows nothing about 802.11n and it will remain
that way.

  Luis