Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [PATCH] iw: add support to print HT40-/+ on channels
Date: Wed, 18 Mar 2009 23:10:28 -0700	[thread overview]
Message-ID: <43e72e890903182310o58cf15f9yeeba8c86c45627d7@mail.gmail.com> (raw)
In-Reply-To: <1237442241-29803-1-git-send-email-lrodriguez@atheros.com>

On Wed, Mar 18, 2009 at 10:57 PM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> You don't have to guess now if your channels support HT40-/+ now.
> This also helps with regulatory testing.

Oh and here's a screenshot:

When a country doesn't allow HT40 at all, you'll see:

                Frequencies:
                        * 2412 MHz [1] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2417 MHz [2] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2422 MHz [3] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2427 MHz [4] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2432 MHz [5] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2437 MHz [6] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2442 MHz [7] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2447 MHz [8] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2452 MHz [9] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2457 MHz [10] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2462 MHz [11] (27.0 dBm / 20 MHz) (HT40 disallowed)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)

When HT40 is allowed but due to band edges either HT40- or HT4+ is not allowed:

                Frequencies:
                        * 2412 MHz [1] (27.0 dBm / 20 MHz) (HT40- disallowed)
                        * 2417 MHz [2] (27.0 dBm / 20 MHz) (HT40- disallowed)
                        * 2422 MHz [3] (27.0 dBm / 20 MHz) (HT40- disallowed)
                        * 2427 MHz [4] (27.0 dBm / 20 MHz) (HT40- disallowed)
                        * 2432 MHz [5] (27.0 dBm / 20 MHz)
                        * 2437 MHz [6] (27.0 dBm / 20 MHz)
                        * 2442 MHz [7] (27.0 dBm / 20 MHz)
                        * 2447 MHz [8] (27.0 dBm / 20 MHz) (HT40+ disallowed)
                        * 2452 MHz [9] (27.0 dBm / 20 MHz) (HT40+ disallowed)
                        * 2457 MHz [10] (27.0 dBm / 20 MHz) (HT40+ disallowed)
                        * 2462 MHz [11] (27.0 dBm / 20 MHz) (HT40+ disallowed)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)

  Luis

  reply	other threads:[~2009-03-19  6:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  5:57 [PATCH] iw: add support to print HT40-/+ on channels Luis R. Rodriguez
2009-03-19  6:10 ` Luis R. Rodriguez [this message]
2009-03-19  9:19   ` Johannes Berg
2009-03-19  9:25     ` Luis R. Rodriguez
2009-03-19  9:36       ` Johannes Berg
2009-03-19  9:45         ` 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=43e72e890903182310o58cf15f9yeeba8c86c45627d7@mail.gmail.com \
    --to=lrodriguez@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox