From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Fri, 30 Oct 2009 07:31:41 -0700 Subject: [ath9k-devel] getting 11n to work? In-Reply-To: <20091030132909.05afb24b@bnc.JUSTUS> References: <20091028204321.5dee58ad@bnc.JUSTUS> <20091029172259.33ea40cd@bnc.JUSTUS> <20091029145114.GA20419@tux> <20091030132909.05afb24b@bnc.JUSTUS> Message-ID: <20091030143141.GA4929@tux> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Thu, Oct 29, 2009 at 08:29:09PM -0700, bnc at netspeed.com.au wrote: > Luis, > I understood the difference between the two lists. > I also understood from your previous remarks that because I had a > single stream chip mcs7 was all I could get. > Does this prevent me from using 11n though? No, MCS 1-7 are for 11n, what you have is an 802.11n single stream device. > I am currently doing a compile on another laptop which I am pretty sure > is multistream, so will test there too. > > I also noticed that from the list you get > HT MCS set: ff 00 00 00 00 00 00 00 00 00 00 00 > but on the multistream you get > HT MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 > What does the second set of ff mean? The MCS set is parsed and is where we get the supported MCS indexes. I am too lazy to check the exact location of the second ff here but mostl likely it parse out to the other set of MCS indexes. In other words you can ignore the MCS set print out as it is already parsed by iw list anyway. Luis