Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iw: add support to print HT40-/+ on channels
Date: Thu, 19 Mar 2009 02:45:21 -0700	[thread overview]
Message-ID: <43e72e890903190245r68003a45q2ce05e0ddeabc033@mail.gmail.com> (raw)
In-Reply-To: <1237455413.5100.55.camel@johannes.local>

On Thu, Mar 19, 2009 at 2:36 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Thu, 2009-03-19 at 02:25 -0700, Luis R. Rodriguez wrote:
>
>> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 * 2432 MHz [5] (27.0 dBm / 20 MHz)
>> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 * 2437 MHz [6] (27.0 dBm / 20 MHz)
>> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 * 2442 MHz [7] (27.0 dBm / 20 MHz)
>
>> > Eh, that doesn't look right. What's with 2432-2443 MHz?
>>
>> It means you get HT40-/+ allowed. Do we want to show if we have it a=
llowed?
>
> What's with the /20mhz though?

Right, so that would mean you're clear regulatory wise to use the
entire 20 MHz for that channel. At a later time perhaps a custom
target bandwidth might be desired, then the regulatory bandwidth check
could be reduced. I'm not sure how we'll do this yet but if we keep
the bandwidth this lets us keep the max per channel and then easily
determine which smaller target bandwidths would be allowed.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-03-19  9:45 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
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 [this message]

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=43e72e890903190245r68003a45q2ce05e0ddeabc033@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