From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] getting 11n to work?
Date: Fri, 30 Oct 2009 07:31:41 -0700 [thread overview]
Message-ID: <20091030143141.GA4929@tux> (raw)
In-Reply-To: <20091030132909.05afb24b@bnc.JUSTUS>
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
next prev parent reply other threads:[~2009-10-30 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 10:43 [ath9k-devel] getting 11n to work? bnc at astronomicalresearchaustralia.org
2009-10-29 7:22 ` bnc at netspeed.com.au
2009-10-29 14:51 ` Luis R. Rodriguez
2009-10-30 3:29 ` bnc at netspeed.com.au
2009-10-30 14:31 ` Luis R. Rodriguez [this message]
2009-10-30 14:51 ` bnc at netspeed.com.au
2009-10-30 15:03 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091030143141.GA4929@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.