All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: allow disabling 40MHz on 2.4GHz
Date: Tue, 01 Dec 2009 13:17:26 -0500	[thread overview]
Message-ID: <1259691446.4806.12.camel@mj> (raw)
In-Reply-To: <1259688582.32171.97.camel@johannes.local>

On Tue, 2009-12-01 at 18:29 +0100, Johannes Berg wrote:
> In some situations it is required that a system be
> configured with no support for 40 MHz channels in
> the 2.4 GHz band. Rather than imposing any such
> restrictions on everybody, allow configuration a
> system like that with a module parameter. It is
> writable at runtime but only takes effect at the
> time of the next association.

That looks like a hack to me.

Maybe it should be treated like other CRDA flags?  In fact, you can find
this in dbparse.py in the wireless-regdb sources:

    # hole at bit 9. FIXME: Where is NO-HT40 defined?
    'NO-HT40':          1<<10,

However, there are no other references to NO-HT40 in the wireless-regdb
or CRDA sources.  I assume it's not implemented.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-12-01 18:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 17:29 [PATCH] mac80211: allow disabling 40MHz on 2.4GHz Johannes Berg
2009-12-01 18:17 ` Pavel Roskin [this message]
2009-12-01 18:27   ` Johannes Berg
2009-12-01 19:18     ` Luis R. Rodriguez
2009-12-02  1:19       ` Pavel Roskin
2009-12-02  1:43         ` Johannes Berg
2009-12-02  4:26           ` Pavel Roskin

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=1259691446.4806.12.camel@mj \
    --to=proski@gnu.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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.